https://bugs.kde.org/show_bug.cgi?id=390175
Bug ID: 390175 Summary: Valgrind internal assertion failure on program that runs normally Product: valgrind Version: 3.13.0 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: kdeb...@cneufeld.ca Target Milestone: --- Created attachment 110491 --> https://bugs.kde.org/attachment.cgi?id=110491&action=edit Valgrind (memcheck) output leading to crash Fails in memcheck and massif. I did a massif run, then made some changes intended to reduce memory consumption. On the second run, massif asserted. I ran memcheck to look for problems, and that also asserted. Assertion is valgrind: m_oset.c:156 (elem_of_node): Assertion 'n->magic == OSET_MAGIC' failed. valgrind: bad magic on node 0x111E5A8FF0 = 0 (expected 5b1f) The program uses about 20GB RSS. The changes I made involved some de-duping of compound structures inside larger data objects. This results in a quite large number of allocations. Before the crash, memcheck prints two warnings about a conditional jump depending on uninitialized values. Then several warnings about large address ranges, then a crash report. I'm attaching the relevant output from memcheck. -- You are receiving this mail because: You are watching all bug changes.