-
Type: Bug
-
Resolution: Won't Fix
-
Priority: Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: Internal Code, Logging
-
ALL
-
Dev Tools 2020-01-13
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.