[SERVER-3612] Add a new_handler that aborts on bad_alloc Created: 16/Aug/11 Updated: 11/Jul/16 Resolved: 14/Sep/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Stability |
| Affects Version/s: | None |
| Fix Version/s: | 2.1.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Mathias Stearn |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 0 | ||||||||||||
| Description |
|
Currently we usually segfault on out of memory conditions and users tend to only post the segfault backtrace and don't notice the bad_alloc line. |
| Comments |
| Comment by Mathias Stearn [ 14/Sep/11 ] |
|
to test, add this line somewhere: new char[1LL<<40]; |
| Comment by auto [ 14/Sep/11 ] |
|
Author: {u'login': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: Add a new_handler to print stack and exit when new fails |