#16958: MPolynomial eval mem leak
-------------------------------------+-------------------------------------
       Reporter:  vbraun             |        Owner:
           Type:  defect             |       Status:  needs_work
       Priority:  major              |    Milestone:  sage-6.4
      Component:  algebra            |   Resolution:
       Keywords:                     |    Merged in:
        Authors:  Volker Braun       |    Reviewers:
Report Upstream:  N/A                |  Work issues:
         Branch:                     |       Commit:
  u/vbraun/mpolynomial_eval_mem_leak |  14061a1d40e8a27d86eac6dd91559b0131f9fe55
   Dependencies:                     |     Stopgaps:
-------------------------------------+-------------------------------------

Comment (by nbruin):

 Replying to [comment:4 vbraun]:
 > Mmm got another segfault elsewhere..
 That doesn't surprise me. We tried to properly interface with
 libsingular's reference counting before and, while we came close, it ended
 up being a rather nightmarish experience. See #13447.

 I am still quite hopeful that this can be fixed *if the right experts get
 in the same room* for a couple of days (either that or people will find
 out if libsingular's reference counting is fundamentally broken).

 (note that #13447 is about garbage collecting rings, which are probably a
 little more complicated data structures. Nonetheless, there may well be
 components in common).

--
Ticket URL: <http://trac.sagemath.org/ticket/16958#comment:7>
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.

Reply via email to