graph is cutted of - is it a bug? #488
Unanswered
mrQanderson
asked this question in
Q&A
Replies: 1 comment 1 reply
-
This situation means that there are likely some native (non python) allocations happening under the main function. As by default these are not tracked the stack for them corresponds to the latest known python frame, in this case, main. This means that these allocation are likely happening in native threads. To show them you need to run memray with --native. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi all!
Could you please, kindly explain me.
Sometimes I noticed that my graph is placed only on some part of the page. And heap size memory is much more high than usual (in 2 times more). But if I rerun the CI job in Gitlab where test process is setup on shared runner - then could be fine.
I attached the original HTML file.
grapth_artifacts.zip
Beta Was this translation helpful? Give feedback.
All reactions