JDK-8067946 : StackYellowPages and StackRedPages have no effect on Windows
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 9
  • Priority: P4
  • Status: Resolved
  • Resolution: Won't Fix
  • OS: windows
  • Submitted: 2014-12-19
  • Updated: 2024-09-10
  • Resolved: 2018-01-04
Related Reports
Duplicate :  
JDK-8213567 - [Graal] ReservedStackAccessTest fails with AssertionError: FAILED: ReentrantLock 419 looks corrupted
Duplicate :  
JDK-8156538 - Metaspace stress test crashes VM with stack overflow
Duplicate :  
JDK-8157521 - VM crashes on Windows instead of throwing StackOverflowError
Duplicate :  
JDK-8339569 - [Windows] Guard zone should use PAGE_NOACCESS instead of PAGE_GUARD
Relates :  
JDK-8157924 - java/lang/invoke/ThrowExceptionsTest.java failed with EXCEPTION_STACK_OVERFLOW
Description
VM flags StackYellowPages and StackRedPages have no effect on Windows.

No matter if we configure the yellow and red pages or not, the EXCEPTION_STACK_OVERFLOW is only thrown when stackbanging causes the last page from the original reservation (which means Hotspot is getting default Windows behaviour).
Comments
I can confirm that SetThreadStackGuarantee does seem to change the size of the Windows red zone, however in my experiments Windows still adds an additional page, and it may enforce a minimum red zone size, so choosing the correct value seems to be trial and error without better documentation on exactly what SetThreadStackGuarantee does.
20-08-2024
This is not on our list of current priorities. If there are additional specific customer requirements, we will consider reopening this issue. Closing as WNF.
04-01-2018
Once this issue is fixed, the implementation of the Reserved Stack Area (JDK-8046936) should be completed for the Windows platform.
23-11-2015
Is there are a simple summary of why the red/yellow pages have no affect, and why we have never detected this?
09-11-2015