Pablo Galindo Salgado
Pablo Galindo Salgado
Agreed, also this is something that redistributors can easily do by setting CFLAGS or similar on they custom builds if they are ok sacrificing debugging / profilings capabilities.
Also if I recall correctly this only happens with the debug version of the interpreter no?
Closing as probably we are not going to do it
> Of course, the code is yours, but to me this would seem a better architecture. It's better in the sense that's more modular and allows to do what you...
Update: we agreed that this makes sense to do and we will investigate ways to handle the complexity. Not sure how much it will take but we will probably do...
Thanks for the report and the follow ups! I will investigate nevertheless in case it’s a transient failure
Played a bit and couldn't reproduce, so I am closing this. Let us know if this happens again
I will look at the flamegraphs in detail tomorrow. In the meantime, to be able to better understand what's going on, do you mind sending us some reproducer or snippet...
Notice that memray tracks memory in two ways (see https://bloomberg.github.io/memray/memory.html): * Heap memory: intercepting allocators directly and accounting for the memory every time the allocator is called. * Resident size:...
> Also, I don't exactly understand the order of frames. It doesn't seem to be ordered by most allocated memory, but it also doesn't seem to be ordered by time....