Repository navigation
tracemalloc: remove arbitrary limit of 100 frames #63985
Description
| BPO | 19786 |
|---|---|
| Nosy | @vstinner |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = <Date 2013-11-27.21:30:57.215>
created_at = <Date 2013-11-25.23:49:46.921>
labels = []
title = 'tracemalloc: remove arbitrary limit of 100 frames'
updated_at = <Date 2013-11-27.21:34:37.099>
user = 'https://github.com/vstinner'bugs.python.org fields:
activity = <Date 2013-11-27.21:34:37.099>
actor = 'vstinner'
assignee = 'none'
closed = True
closed_date = <Date 2013-11-27.21:30:57.215>
closer = 'python-dev'
components = []
creation = <Date 2013-11-25.23:49:46.921>
creator = 'vstinner'
dependencies = []
files = []
hgrepos = []
issue_num = 19786
keywords = []
message_count = 3.0
messages = ['204440', '204615', '204616']
nosy_count = 3.0
nosy_names = ['vstinner', 'Arfrever', 'python-dev']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = 'resolved'
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue19786'
versions = ['Python 3.4']
Activity
vstinner commentedon Nov 25, 2013
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.
python-dev commentedon Nov 27, 2013
New changeset eead17ba32d8 by Victor Stinner in branch 'default':
Closes bpo-19786: tracemalloc, remove the arbitrary limit of 100 frames
http://hg.python.org/cpython/rev/eead17ba32d8
vstinner commentedon Nov 27, 2013
I ran 17 random tests of the Python test suite: the longest traceback contains 85 frames, the mean is 31.6 frames.