-
|
Based on the numbers attached in the screenshot, I assume we're not memory constrained on any of this stuff, but I see ??? for the largest allocation. Any idea why that's happening? We are curious because its a large allocation, it will be quite helpful if you point out what leads to the loss of allocation info. Also, it will be great if you can mention a way we retrieve the details of function and location that got obfuscated by ???
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
That means that the allocation occurred at a point when there were no Python frames on the thread's stack. If you enable native tracking you can get capture a stack that includes native frames as well as Python frames, which would help you tell where that allocation occurred as long as debug symbols are available for whatever library it occurred in (probably libc or libpython, since that seems to have happened early in the creation of a new thread). |
Beta Was this translation helpful? Give feedback.
That means that the allocation occurred at a point when there were no Python frames on the thread's stack. If you enable native tracking you can get capture a stack that includes native frames as well as Python frames, which would help you tell where that allocation occurred as long as debug symbols are available for whatever library it occurred in (probably libc or libpython, since that seems to have happened early in the creation of a new thread).