https://bugs.kde.org/show_bug.cgi?id=378494
--- Comment #3 from Milian Wolff <m...@milianw.de> ---
ah, I can reproduce the issue with your test code even without heaptrack, when
I slightly modify it:
at the very start of main, add:
auto t = std::thread([]() { while(true)
{std::this_thread::sleep_for(std::chrono::milliseconds(1000));} });
this is essentially what happens when `char *p = new char[1000];` is handled by
heaptrack - we spin up the timer thread and that then messes with your code.
I'm not a C person, and also have close to zero experience with signals. can
you explain the behavior with the above change excluding heaptrack?
--
You are receiving this mail because:
You are watching all bug changes.
