[SERVER-14014] Mongodb Segmentation fault Created: 21/May/14 Updated: 10/Dec/14 Resolved: 22/May/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | 2.6.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pontus Naimell | Assignee: | Ramon Fernandez Marina |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Operating System: | Linux | ||||||||
| Participants: | |||||||||
| Description |
|
Running this script caused a seg fault on 2.6.0:
Maybe not very good to iterate like this but a seg fault is not good. |
| Comments |
| Comment by Ramon Fernandez Marina [ 22/May/14 ] | |
|
pontus I'm able to reproduce the segfault using 2.6.0. Looks like you're running into | |
| Comment by Pontus Naimell [ 22/May/14 ] | |
|
The log really says nothing else of interest Many of these 2014-05-21T07:56:11.212+0000 [conn209501] SEVERE: Invalid access at address: 0x20039e0e02 Looking further back Further back more "connection accepted". This system is under development right now so there is no real usage right now. The only SEVERE in the logfile is the one i sent you My estimates on the collection size looks like this. No core dumped { , | |
| Comment by Ramon Fernandez Marina [ 21/May/14 ] | |
|
Hi Pontus, I'm unable to reproduce the behavior you describe on 2.6.0 or 2.6.1 using a collection with 1000 sample documents. How many documents do you have in your collection? Also, can you please send us some sample documents? For example:
The log you sent is truncated, and may be useful to see if there are some other error messages earlier that might help us understand what's going on – can you send us a complete log as well? |