[SERVER-16202] printSignalAndBacktrace allocates memory Created: 17/Nov/14 Updated: 02/Jan/20 Resolved: 02/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code, Logging |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Eric Milkie | Assignee: | Billy Donahue |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | platforms-needs-37-triage | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Sprint: | Dev Tools 2020-01-13 |
| Participants: |
| Description |
|
We can deadlock with ourselves if printSignalAndBacktrace is triggered by an out-of-memory condition. It allocates memory because we connect the "global" ramlog to the global log domain at startup, and the ramlog allocates memory when its appender is called. |
| Comments |
| Comment by Andy Schwerin [ 30/Dec/19 ] |
|
I suggest we close this “won’t fix” |
| Comment by Andy Schwerin [ 17/Nov/14 ] |
|
A possible solution is to change the RamLogAppender to not allocate memory. It shouldn't need to, but it would require restructuring. |