➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2013-11-25 23:49 by vstinner, last changed 2022-04-11 14:57 by admin. This issue is now closed.
| Messages (3) | |||
|---|---|---|---|
| msg204440 - (view) | Author: STINNER Victor (vstinner) *  |
Date: 2013-11-25 23:49 | |
It should be possible to collect more than 100 frames per traceback (even it is much slower and uses much more memory). I prepared the code to make it possible. Now only one thread should call traceback_new() at the same time, and the maximum number of frames is fixed while tracemalloc is tracing. I will work on a patch. |
|||
| msg204615 - (view) | Author: Roundup Robot (python-dev)  |
Date: 2013-11-27 21:30 | |
New changeset eead17ba32d8 by Victor Stinner in branch 'default': Closes #19786: tracemalloc, remove the arbitrary limit of 100 frames http://hg.python.org/cpython/rev/eead17ba32d8 |
|||
| msg204616 - (view) | Author: STINNER Victor (vstinner) * |
Date: 2013-11-27 21:34 | |
I ran 17 random tests of the Python test suite: the longest traceback contains 85 frames, the mean is 31.6 frames. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:57:54 | admin | set | github: 63985 |
| 2013-11-27 21:34:37 | vstinner | set | messages: + msg204616 |
| 2013-11-27 21:30:57 | python-dev | set | status: open -> closed nosy: + python-dev messages: + msg204615 resolution: fixed stage: resolved |
| 2013-11-26 02:27:50 | Arfrever | set | nosy:
+ Arfrever |
| 2013-11-25 23:49:46 | vstinner | create | |