[issue1565525] gc allowing tracebacks to eat up memory

2010-06-25 Thread Martin v . Löwis
Changes by Martin v. Löwis : -- resolution: -> wont fix status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list maili

[issue1565525] gc allowing tracebacks to eat up memory

2010-06-25 Thread Terry J. Reedy
Terry J. Reedy added the comment: Given comments like "I'm still having problems figuring out what the bug is that you are reporting. (Martin)" and "I must repeat that there is no simple-minded way to 'repair' this. (Tim)", and subsequent changes to Python, should this still be open? If so, f

[issue1565525] gc allowing tracebacks to eat up memory

2009-01-13 Thread Greg Hazel
Greg Hazel added the comment: STINNER Victor> Do you need the original traceback? Why not only raising the exception? If the exception was captured in one stack, and is being re-raised in another. It would be more useful to see the two stacks appended instead of just the place where it was r

[issue1565525] gc allowing tracebacks to eat up memory

2009-01-13 Thread STINNER Victor
STINNER Victor added the comment: Greg Hazel> But a list of strings is not re-raisable Do you need the original traceback? Why not only raising the exception? Eg. import sys try: raise Exception("hm!") except: t, v, tb = sys.exc_info() raise v

[issue1565525] gc allowing tracebacks to eat up memory

2009-01-13 Thread STINNER Victor
STINNER Victor added the comment: I tried to remove the frame from the traceback type (to keep only the filename and code name), but many functions rely on the frame object. Some examples: Lib/unittest.py: class TestResult(object): def _is_relevant_tb_level(self, tb): return

[issue1565525] gc allowing tracebacks to eat up memory

2009-01-13 Thread Greg Hazel
Greg Hazel added the comment: But a list of strings is not re-raisable. The co_filename, co_name, and such used to print a traceback are not dependent on the locals or globals. ___ Python tracker __

[issue1565525] gc allowing tracebacks to eat up memory

2009-01-13 Thread STINNER Victor
STINNER Victor added the comment: I wrote a patch to support .tb_frame=None. It works but the traceback becomes useless because you have unable to display the traceback. The frame is used by tb_printinternal() to get the filename (co_filename) and the code name (co_name). I also tried: w

[issue1565525] gc allowing tracebacks to eat up memory

2008-10-06 Thread STINNER Victor
STINNER Victor <[EMAIL PROTECTED]> added the comment: Similar issue: issue4034 proposes to be able to set tb.tb_frame=None. It's easy to implement this, I can write a patch for this. -- nosy: +haypo ___ Python tracker <[EMAIL PROTECTED]>

[issue1565525] gc allowing tracebacks to eat up memory

2008-10-04 Thread Greg Hazel
Greg Hazel <[EMAIL PROTECTED]> added the comment: Or, being able to remove the references to the locals and globals from the traceback would be sufficient. Something like this: try: raise Exception() except: t, v, tb = sys.exc_info() tbi = tb while tbi: tbi.tb_frame.f_l