Memray shows <stack trace unavailable for allocations in pre-existing threads
Memray shows <stack trace unavailable for allocations in pre-existing threads: a task in LegoFlow-SWE (Harbor dataset). When tracking memory with memray.Tracker , if any threads are already executing code at the moment tracking begins, allocations made by those threads are reported as <stack trace…
The task
When tracking memory with `memray.Tracker`, if any threads are already executing code at the moment tracking begins, allocations made by those threads are reported as `<stack trace unavailable>` instead of displaying the real Python call stack. This makes it impossible to see where the memory is being allocated in…
Part of Lego-X/LegoFlow-SWE.