[SERVER-13303] Crash during garbage collection Created: 21/Mar/14 Updated: 10/Dec/14 Resolved: 15/May/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | JavaScript |
| Affects Version/s: | 2.4.9 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Andrew Poland [X] | Assignee: | Mathias Stearn |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | crash | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
When running serverside javascript with logging after running anywhere between 20 minutes to 2 hours mongo crashes and logs a stack trace as shown in table below. The function does a number of queries and inserts. The logging appears to indicate that it is thrown just before an add. The time it takes for this to occur seems to decrease if logging is added to the function. Where logging is performed with print and printjson.
|
| Comments |
| Comment by Benety Goh [ 15/May/14 ] |
|
fixed by this recent commit: Message: |
| Comment by Mathias Stearn [ 21/Apr/14 ] |
|
AndrewP Have you had a change to test the patch? |
| Comment by Andrew Poland [X] [ 25/Mar/14 ] |
|
thanks, Yes, we are running the script through db.eval(). I will try the patch and if the crash still occurs create a dump. |
| Comment by Mathias Stearn [ 25/Mar/14 ] |
|
Unfortunately, I don't think I will be able to repro without documents to test this with. Would it be possible to get a dump of data (or generation script) that is known to exhibit this issue? If it is sensitive data we can send you a secure way to upload it. Also, how exactly are you running it. The crash looks like it is in the server so I'm assuming that you aren't just running it in the shell. Are you running that function inside a db.eval()? Additionally, we have a patch that fixes a related bug. However I'm not sure if it will solve the issue you are seeing. I'm attaching both the 2.4 and 2.6 versions of this patch if you are able to test it. |
| Comment by Mathias Stearn [ 21/Mar/14 ] |
|
Is there any way you could give us a script that reproduces this behavior? |