#13731: Fix libsingular memory management
--------------------------------------------------------------+-------------
Reporter: nbruin | Owner:
rlm
Type: defect | Status:
new
Priority: major | Milestone:
sage-5.6
Component: memleak | Resolution:
Keywords: | Work issues:
Report Upstream: Fixed upstream, in a later stable release. | Reviewers:
Authors: Nils Bruin, Simon King | Merged in:
Dependencies: | Stopgaps:
--------------------------------------------------------------+-------------
Comment (by SimonKing):
Replying to [comment:109 nbruin]:
> That variable doesn't do anything on OSX, so congratulations that xalloc
works on OSX, but you haven't done stringent memory checking yet. Try
> {{{
> export DYLD_INSERT_LIBRARIES=/usr/lib/libgmalloc.dylib
> }}}
> instead. see `man libgmalloc` for various options to select what should
be guarded.
> (warning: It will run MUCH slower and take MUCH more memory. It seems
gmalloc is about as strict as `ElectricFence` which is also incredibly
slow. Valgrind is speedy by comparison)
Thank you!
First result:
{{{
----------------------------------------------------------------------
| Sage Version 5.5.rc0, Release Date: 2012-11-17 |
| Type "notebook()" for the browser-based notebook interface. |
| Type "help()" for help. |
----------------------------------------------------------------------
**********************************************************************
* *
* Warning: this is a prerelease version, and it may be unstable. *
* *
**********************************************************************
GuardMalloc: Allocations will be placed on 16 byte boundaries.
GuardMalloc: - Some buffer overruns may not be noticed.
GuardMalloc: - Applications using vector instructions (e.g., SSE or
Altivec) should work.
GuardMalloc: GuardMalloc version 23
GuardMalloc: Allocations will be placed on 16 byte boundaries.
GuardMalloc: - Some buffer overruns may not be noticed.
GuardMalloc: - Applications using vector instructions (e.g., SSE or
Altivec) should work.
GuardMalloc: GuardMalloc version 23
GuardMalloc: Allocations will be placed on 16 byte boundaries.
GuardMalloc: - Some buffer overruns may not be noticed.
GuardMalloc: - Applications using vector instructions (e.g., SSE or
Altivec) should work.
GuardMalloc: GuardMalloc version 23
GuardMalloc: Allocations will be placed on 16 byte boundaries.
GuardMalloc: - Some buffer overruns may not be noticed.
GuardMalloc: - Applications using vector instructions (e.g., SSE or
Altivec) should work.
GuardMalloc: GuardMalloc version 23
sage: A.<x,y> = FreeAlgebra(QQ, 2)
sage: P.<x,y> = A.g_algebra({y*x:-x*y})
sage: x*y
x*y
sage: quit
Exiting Sage (CPU time 0m24.65s, Wall time 1m15.86s).
}}}
So, the bug really is fixed, on OSX as well.
Second result: Yes, it is ''incredibly'' slow!
Nevertheless, I just started `sage -testall` under gmalloc on bsd.math.
Let's see whether it will finish this year...
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13731#comment:110>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
