https://bugs.kde.org/show_bug.cgi?id=466524
--- Comment #2 from michael <reeves...@gmail.com> --- Thanks. The valigrind information is actually more value in this type of situation as shows memory management issues that may otherwise be hard to find. In this a shared_ptr was being converted to raw form which left a dangling pointer in DiffTextWindowData. Knowing where the crash happens often isn't enough for a case like this. Needed to the allocation and deallocation points as well. This has been corrected locally but something about my setup/usage doesn't trigger the issue. -- You are receiving this mail because: You are watching all bug changes.
