If you're actually seeing faiures with 32k, then 48k is too conservative. I suggest 128k.
I tried once to increase the limit to 64k, but without a failing test it didn't get any support. The presence of native thread local variables is the biggest reason for blowing the stack; no limit is actually safe! That's a deep hotspot/glibc problem. On Wed, Apr 13, 2016 at 8:42 AM, Roger Riggs <roger.ri...@oracle.com> wrote: > Please review an increase in the default stack size of the Process reaper > thread to 48K from 32k. > Some tests with various VM arguments are failing intermittently. > The failures are not reproducible. > > Webrev: > http://cr.openjdk.java.net/~rriggs/webrev-reaper-stack-8086278/ > > Issue: > https://bugs.openjdk.java.net/browse/JDK-8086278 > > Thanks, Roger >
