Bug ID: JDK-8350284 WebKit 620.1 crashes on startup on Windows x86 32-bit

Versions (Unresolved/Resolved/Fixed)

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.

Other
jfx24.0.2Fixed

WebKit 620.1 crashes on startup when running a 32-bit binary on Windows. This can be reproduced running HelloWebView with any .html file. For example:

$ java HelloWebView file:///C:/path/to/simple.html

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x1bc905e8, pid=19932, tid=0x000094b4
#
# JRE version: Java(TM) SE Runtime Environment (8.0) (build 1.8.0_451-b06)
# Java VM: Java HotSpot(TM) Client VM (25.451-b06 mixed mode windows-x86 )
# Problematic frame:
# C  [jfxwebkit.dll+0xe505e8]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\Users\kcr\dev\javafx\tmp\hs_err_pid19932.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

I'll attach a log file.

NOTE: The JDK 8 certified configurations page recommends against running WebKit using 32-bit binaries (due to other known problems).

[~kcr] Thanks, Kevin! Currently I'm not going to backport this to jfx21u and jfx17u.
09-04-2025
[jfx24u-fix-request] Approval Request from Jay Bhaskar the patch fixes issue of web view startup on window i586 machine but need to be in sync with mainline
09-04-2025
A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jfx24u/pull/18 Date: 2025-04-09 12:02:20 +0000
09-04-2025
Changeset: d31f764b Branch: master Author: Roman Marchenko <rmarchenko@openjdk.org> Committer: Kevin Rushforth <kcr@openjdk.org> Date: 2025-04-08 19:02:27 +0000 URL: https://git.openjdk.org/jfx/commit/d31f764b565cafdb6cafe88a9676ffba8cb7cdbb
08-04-2025
[~rmarchenko] Thank you for submitting a PR for this. Once approved and integrated into jfx:master, we'll backport to jfx24u. You can do the backport to jfx21u and jfx17u if you want it in those release trains.
08-04-2025
A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jfx/pull/1764 Date: 2025-04-08 07:48:19 +0000
08-04-2025
All the crashes I see are on "movaps" instruction, like "movaps xmmword ptr [esi+0x30], xmm0". "movaps" must operate with aligned addresses as “When the source or destination operand is a memory operand, the operand must be aligned on a 16-byte boundary or a general-protection exception (#GP) is generated” written in docs. When crashes, ESI contains value like 0x27DB63A8, so it doesn’t seem aligned to 16-byte boundary. The line "siginfo: ExceptionCode=0xc0000005, reading address 0xffffffff" implicitly says it is GP, not a real "reading address 0xffffffff". It might be related to clang-cl bug, see https://github.com/llvm/llvm-project/issues/55844 The workaround is to disable SSE when building 32bit on Windows. (-mno-sse) Does it looks like the appropriate fix?
31-03-2025
Thanks, Kevin,we observe the same symptoms.
20-03-2025

Causes :	JDK-8340322 - Update WebKit to 620.1
Relates :	JDK-8352257 - test.javafx.scene.web.LeakTest crash after webkit 620.1 update