mirror of
https://github.com/LadybirdBrowser/ladybird.git
synced 2025-01-08 20:32:56 +03:00
01c75e3a34
There were a few cases where we could end up logging profiling events before or after the associated process or thread exists in the profile: After enabling profiling we might end up with CPU samples before we had a chance to synthesize process/thread creation events. After a thread exits we would still log associated kmalloc/kfree events. Instead we now just ignore those events. |
||
---|---|---|
.. | ||
Heap.h | ||
kmalloc.cpp | ||
kmalloc.h | ||
SlabAllocator.cpp | ||
SlabAllocator.h |