#18905: fix more leaks found in #18897
-------------------------------------+-------------------------------------
Reporter: dimpase | Owner:
Type: defect | Status: needs_work
Priority: major | Milestone: sage-6.8
Component: memleak | Resolution:
Keywords: | Merged in:
Authors: Simon King | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/SimonKing/memleak_for_integer_mod_rel_14058|
3ada19d1acf58d1d085c1908b3058de8377901a4
Dependencies: #18897, #14058 | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by SimonKing):
Replying to [comment:39 vdelecroix]:
> Replying to [comment:38 SimonKing]:
> > Replying to [comment:37 vdelecroix]:
> > Could someone verify if it is really the case that tests pass with
"develop", but fail with the branch from here (merged in "develop" of
course)? I currently do not have the bandwidth.
>
> It does fail, see [http://trac.sagemath.org/ticket/14058#comment:62
#14058 comment 62].
Please be clearer. It fails in what setting? Does it only fail with
#14058? Does it also fail with develop? Does it also fail with the branch
from here?
If it fails both here and at #14058, but not with develop, then I reckon
both branches trigger a memory leak that was introduced elsewhere.
--
Ticket URL: <http://trac.sagemath.org/ticket/18905#comment:40>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
