[SERVER-9595] Another occasional segfault in mongo server Created: 06/May/13 Updated: 10/Dec/14 Resolved: 16/May/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | JavaScript, MapReduce |
| Affects Version/s: | 2.2.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ian Greenhoe | Assignee: | Ben Becker |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux Centos 6.3 |
||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | This one seems similar to, but not the same as Server under heavy load, with a complex M/R function. I can't give more precise STR then that, unfortunately, as we have multiple complex M/R functions. When we have more precise information, we will attach it to this bug. |
||||||||
| Participants: | |||||||||
| Description |
|
Mon Apr 22 12:14:34 Invalid access at address: 0 from thread: conn2 Mon Apr 22 12:14:34 Got signal: 11 (Segmentation fault: 11). Mon Apr 22 12:14:34 Backtrace: |
| Comments |
| Comment by Ben Becker [ 16/May/13 ] |
|
This appears to be due to an allocation failure; similar. SMScope::init() calls two Converter functions which fail to check for error conditions (similar to |