#20624: maximum recursion depth exceeded in MonoDictEraser
-------------------------------+------------------------
       Reporter:  vbraun       |        Owner:
           Type:  defect       |       Status:  new
       Priority:  major        |    Milestone:  sage-7.3
      Component:  misc         |   Resolution:
       Keywords:  random_fail  |    Merged in:
        Authors:               |    Reviewers:
Report Upstream:  N/A          |  Work issues:
         Branch:               |       Commit:
   Dependencies:               |     Stopgaps:
-------------------------------+------------------------

Comment (by nbruin):

 Ah goodie! This brings back fond memories from the ticket from hell
 #10963. Specifically: [http://trac.sagemath.org/ticket/10963#comment:242
 comment:242]. Note that there the (ignored) errors in the Eraser classes
 were a symptom of an overloaded call stack caused by other (basically)
 infinite recursions.

 I'm curious to see what's causing this. If it's actually a too-deep
 recursion in a deletion somewhere, I would be very surprised.

--
Ticket URL: <http://trac.sagemath.org/ticket/20624#comment:1>
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 https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.

Reply via email to