https://bugs.kde.org/show_bug.cgi?id=473695
Milian Wolff <m...@milianw.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|CONFIRMED |RESOLVED
--- Comment #3 from Milian Wolff <m...@milianw.de> ---
The std::terminate call got fixed with this:
commit 74fa950160892b06e26d3358b502a6331c2041bd (HEAD -> master, origin/master,
origin/HEAD)
Author: Milian Wolff <m...@milianw.de>
Date: Thu Aug 24 09:29:09 2023 +0200
Don't use exceptions when timer thread fails to lock
This is a bit unweildy without C++17 and std::optional, but it gets
the job done. Apparently throwing exceptions doesn't work from within
heaptrack when it's injected into a flutter binary, for unclear
reasons. Maybe due to [1] but that's supposedly fixed in newer flutter
versions already. But as soon as we throw, we would terminate in the
context of a terminate.
[1]: https://github.com/flutter/flutter/issues/66575
--
You are receiving this mail because:
You are watching all bug changes.
