While working on JDK-8068614 I learned that the reported max stack trace depth is 32 frames (on Mac OS X), but currently the produced stack depth, in the test, is only 12 frames deep.
To really stress out the code at the time of memory exhaustion we should ensure that the stack is as deep as it can possibly can be.
To really stress out the code at the time of memory exhaustion we should ensure that the stack is as deep as it can possibly can be.
- relates to
-
JDK-8068614 [TESTBUG] OOMProductionAnonymousTrace creates a broken stack trace
-
- Resolved
-