[SERVER-26889] Incorrect memory access on 3.0.13 triggers segmentation fault Created: 02/Nov/16 Updated: 20/Jan/17 Resolved: 03/Nov/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.0.13 |
| Fix Version/s: | 3.0.14 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Burak Ozyurt | Assignee: | Keith Bostic (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Case: | (copied to CRM) | ||||||||||||
| Description |
| Comments |
| Comment by Burak Ozyurt [ 03/Nov/16 ] |
|
I have upgraded to 3.2.10 and have not encountered any issue so far. – |
| Comment by Ramon Fernandez Marina [ 03/Nov/16 ] |
|
bozyurt, we've identified the root cause for this bug and checked in a fix that will be available very soon. As I mentioned above, the workarounds are to either downgrade to 3.0.12, or to upgrade to 3.2.10, neither of which contains this bug. Sorry that you were impacted by this, and thanks for reporting it. Regards, |
| Comment by Githook User [ 03/Nov/16 ] |
|
Author: {u'name': u'Ramon Fernandez', u'email': u'ramon@mongodb.com'}Message: Import wiredtiger: b1aab8db7d80e165d5da80aab0c0403772450997 from branch mongodb-3.0 ref: a5c67bd..b1aab8db7d
|
| Comment by Githook User [ 03/Nov/16 ] |
|
Author: {u'username': u'keithbostic', u'name': u'Keith Bostic', u'email': u'keith.bostic@mongodb.com'}Message: Fix 552a33b (cherry-picked from 521270d). When the commit was merged, |
| Comment by Keith Bostic (Inactive) [ 03/Nov/16 ] |
|
bozyurt, I think we understand this problem and likely won't need your database files. Thank you! |
| Comment by Ramon Fernandez Marina [ 03/Nov/16 ] |
|
bozyurt, I just realized we may need to see the files in your dbpath to troubleshoot this issue, so I've created a private, secure upload portal for you to upload them. They will remain accessible only to MongoDB engineers for the purpose of investigating this bug, and deleted afterwards. Thanks, |
| Comment by Ramon Fernandez Marina [ 02/Nov/16 ] |
|
Sorry to hear you're running into this bozyurt, we're investigating. As a workaround, you may want to consider downgrading to 3.0.12 if the problem doesn't manifest there. The alternative is to upgrade to 3.2.10. thanks, |