mirror of
https://github.com/SerenityOS/serenity
synced 2026-05-09 00:22:43 +02:00
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.
21 KiB
21 KiB