Sorry for the previous comment. After testing with jemalloc and valgrind, I found the problem was caused by a double free within a class destructor, that was being used within an std::unordered_set, so the copy constructor was causing deletions and accesses to the deleted memory. It helped to have the debug compilation of jemalloc, so it would have been helpful to have the equivalent debug compilation of the glibc malloc available, but it may not have enough assert statements to catch this.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1020210 Title: Race condition using ATOMIC_FASTBINS in _int_free causes crash or heap corruption To manage notifications about this bug go to: https://bugs.launchpad.net/eglibc/+bug/1020210/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
