#715: Parents probably not reclaimed due to too much caching
-------------------------------------------------------------------+--------
       Reporter:  robertwb                                         |         
Owner:  somebody                                 
           Type:  defect                                           |        
Status:  needs_review                             
       Priority:  major                                            |     
Milestone:  sage-5.4                                 
      Component:  coercion                                         |    
Resolution:                                           
       Keywords:  weak cache coercion Cernay2012                   |   Work 
issues:                                           
Report Upstream:  N/A                                              |     
Reviewers:  Jean-Pierre Flori, Simon King, Nils Bruin
        Authors:  Simon King, Jean-Pierre Flori                    |     Merged 
in:                                           
   Dependencies:  #9138, #11900, #11599, to be merged with #11521  |      
Stopgaps:                                           
-------------------------------------------------------------------+--------

Comment (by SimonKing):

 Replying to [comment:268 nbruin]:
 > Replying to [comment:265 SimonKing]:
 >
 > > Why do you think so? It is the temporary file created by sage-doctest.
 I had modified sage-doctest so that the location of the temporary file is
 shown, instead of deleting the file - hence, I could copy it and post it
 here.
 >
 > I did the same but got a bigger file (I'm not attaching it because with
 the hardcoded paths it's useless, so you have to extract it yourself
 anyway)
 > {{{
 > duke sage/5.3rc1$ wc failing_test_under_gdb.py
 >   96  283 3714 failing_test_under_gdb.py
 > duke sage/5.3rc1$ wc cachefunc_3730.py
 >  2592 10019 99307 cachefunc_3730.py
 > }}}
 > so I suspect that you edited it. However, if your shorter file is still
 capable of segfaulting, that's fine, of course.

 As I said: It is the file from comment:251, it is ''not'' cachefunc.pyx,
 but just a single test from cachefunc.pyx that suffices to trigger the
 error (which also demonstrates that it is not a side effect of other
 tests).

 > If you do this on the machine where you get the SEGV (i.e., bsd) in the
 doctest,

 Do I get SEGV? Is that a synonym of signal 11?

 > For running under gdb:
 > {{{
 > > gdb --args python -t cachefunc_3730.py
 > [...runs fine...]
 > }}}
 > we already know that that prevents the SEGV from happening.

 Is it preventing it from happening? I thought we have found that some
 signal problem is still present for sub-processes created with
 p_iter_fork.

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

Reply via email to