#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):

 Playing around with [attachment:cachefunc_94107.py]:

 `sage cachefunc_94107.py` also results in that segfault.

 Starting sage and then attaching cachefunc_94107.py to the interactive
 session, I get:
 {{{
 sage: attach ~/SAGE/work/signal11/cachefunc_94107.py
 ---------------------------------------------------------------------------
 SystemExit                                Traceback (most recent call
 last)

 /scratch/sking/sage-5.4.beta0/devel/sage-main/<ipython console> in
 <module>()

 /scratch/sking/sage-5.4.beta0/local/lib/python2.7/site-
 packages/sage/misc/preparser.pyc in load(filename, globals, attach)
    1646
    1647     if fpath.endswith('.py'):
 -> 1648         execfile(fpath, globals)
    1649     elif fpath.endswith('.sage'):
    1650         if (attach and attach_debug_mode) or ((not attach) and
 load_debug_mode):

 /Users/SimonKing/SAGE/work/signal11/cachefunc_94107.py in <module>()
    2588         sys.exit(255)
    2589     quit_sage(verbose=False)
    2590     if runner.failures > 254:
    2591         sys.exit(254)
 -> 2592     sys.exit(runner.failures)

 SystemExit: 0
 Type %exit or %quit to exit IPython (%Exit or %Quit do so
 unconditionally).
 sage:
 }}}
 So, up to here, it more or less looks normal. But when I press Ctrl-D to
 leave the interactive session, I get:
 {{{
 Exiting Sage (CPU time 0m0.70s, Wall time 0m30.10s).
 /scratch/sking/sage-5.4.beta0/spkg/bin/sage: line 336: 97357 Segmentation
 fault      sage-ipython "$@" -i
 }}}
 The "Exiting Sage ..." is printed at the beginning of sage.all.quit_sage.
 Hence, it now seems that (again) leaving Sage is the problem.

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