https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #11 from Matt Fagnani <matthew.fagn...@utoronto.ca> --- Memory leaks were detected with 8-9 definitely lost blocks, 48 indirectly lost blocks, and 19 possibly lost blocks per run. I'm unsure if the segmentation faults are related to those memory leaks. One line I wrote should have been Invalid reads/writes were common at other points in the stack. The invalid reads/writes of freed memory seem to have started earlier in the shutdown process than those which directly caused in the segmentation faults. Memory corruption might have been involved as a result of the use-after-frees. -- You are receiving this mail because: You are watching all bug changes.
