JDK-8242209 : Increase web native thread stack size for x86 mode
- Type: Bug
- Component: javafx
- Sub-Component: web
- Affected Version: 8u231,openjfx15
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: windows
- CPU: x86
- Submitted: 2020-04-06
- Updated: 2020-06-09
- Resolved: 2020-04-11
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 8 | Other |
|---|---|
8u261Fixed  |
openjfx11.0.8Fixed |
Description
CLoop interpreter used in 32-bit Windows uses 87 KB of stack space each time CLoop::execute() is called. For web native threads which has a default stack size of 320 KB, a Stack Overflow Error is raised just after two calls to execute() function. While 64-bit windows has a default stack size of 1 MB. Fix: Increase the thread stack size of web native threads for x86 to 1 MB.
Comments
|