[SERVER-2574] possible memory leak in v8 implementation Created: 17/Feb/11 Updated: 29/May/12 Resolved: 10/Jan/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | JavaScript |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Aaron Staple | Assignee: | Antoine Girbal |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Running parallel/basic.js many times in sequence causes mongod to run out of memory. It is over a long time period, so likely not cursor related. |
| Comments |
| Comment by Antoine Girbal [ 10/Jan/12 ] |
|
tried to reproduce this but couldnt, both res and heap memory seem stable. |
| Comment by Aaron Staple [ 21/Feb/11 ] |
|
valgrind run |