Regarding Ubuntu 15, I think that was a miscommunication somewhere along the line.
The only versions of Ubuntu that we build for are the LTS releases (12.04, 14.04, and 16.04), and the only one of those we have ever built on POWER is 16.04. Other than Ubuntu 16.04, the only other POWER distro we target is RHEL 7.1. So what we are seeing is I think still consistent with either a latent locking bug in MongoDB exposed by the new-to-us lock elision support, or one of the other sorts of issues as mentioned by Adam above. Also, my test run using the disabled lock elision just reached 500 successful runs. I'm going to switch lock elision back on and make sure I start seeing corruption again, but I'm nearly certain that I will. Thanks for the update on the mprotect experiment. It would have been great if that had worked. I think we will be able to share some details on our similar experiments on Monday. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640518 Title: MongoDB Memory corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-5/+bug/1640518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
