[SERVER-7417] Invalid access at address: 0 from thread: journal Created: 18/Oct/12 Updated: 08/Mar/13 Resolved: 09/Nov/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.2.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Bobby J | Assignee: | Eric Milkie |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Ubuntu 12.04 |
||
| Operating System: | Linux |
| Participants: |
| Description |
|
Saving new entries on multiple python processes (via pymongo 2.3), and get the error below. Has happened repeatedly, but not reproducibly. Thu Oct 18 13:56:50 [initandlisten] connection accepted from 127.0.0.1:46942 #18413 Thu Oct 18 13:56:50 Got signal: 11 (Segmentation fault). Thu Oct 18 13:56:50 Backtrace: |
| Comments |
| Comment by Bobby J [ 13/Nov/12 ] |
|
Realized that this occurred during an (unrelated) catastrophic failure of the disk it was using. Given this unique event, I don't think we'll be able to reproduce. Thanks for looking into it. |
| Comment by Eric Milkie [ 23/Oct/12 ] |
|
Hi Bobby. Thanks for reporting this issue. The crash seems to be happening because we're using a null buffer for the temporary storage that the journaling system uses to compress its redo log. Since this buffer is static and protected by a mutex, I'm not yet sure how it could be seen as null during normal program execution. |