-
-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jdk-17+35 crashes with JFileChooser on Win10 #385
Comments
Are you able to try with the latest nightly? https://github.com/adoptium/temurin17-binaries/releases/download/jdk17u-2021-10-25-08-48-beta/OpenJDK17U-jdk_x64_windows_hotspot_2021-10-25-08-48.zip - we have 17.0.1 coming out this week. |
Thanks, Karianna. I checked with the nightly build. The crash does not occur there. Seemingly, it is already solved. Best regards! |
Ok, I did some further testing. The crash occurs in the 32Bit VM but not in the x64. Can't say, if it still occurs with the 32bit VM in the nightlies. I will check with the next official release. |
It still crashes on Windows in 17.0.1 32bit. It is not related to FlatLaf. Occurs also in Windows L&F. There was a change in this area in JDK 17 to access "large Windows icons", which may be responsible for this crash. Maybe this change was never tested on 32 Bit because Oracle distributes only 64 Bit JDKs? Testcase: import javax.swing.JFileChooser;
import javax.swing.SwingUtilities;
import javax.swing.UIManager;
public class FileChooserTest {
public static void main(String[] args) {
try {
UIManager.setLookAndFeel( UIManager.getSystemLookAndFeelClassName() );
} catch( Exception ex ) {
ex.printStackTrace();
}
SwingUtilities.invokeLater(new Runnable() {
@Override
public void run() {
try {
JFileChooser chooser = new JFileChooser();
chooser.showSaveDialog(null);
String file = chooser.getSelectedFile().getName();
System.out.println(file);
} catch (Exception e) {
e.printStackTrace();
}
}
});
}
} |
@karianna This might be a good item for your Microsoft friends to look into upstream :) 32-bit Windows issue. |
Yes - we have David Grieve working on this internally :-) |
As a workaround, set the minimum thread stack size, e.g. -Xss1M
See hotspot/os_cpu/windows_x86/globals_windows_x86.hpp |
We are marking this issue as stale because it has not been updated for a while. This is just a way to keep the support issues queue manageable. |
I think this can be closed because JDK-8277299 is fixed in Java 18 and backported to Java 17.0.3 |
Summary
Invoking JFileChooser leads to crash outside the VM in case, FlatLaF is used as the look and feel.
Steps to reproduce
Minimal code to reproduce:
Expected results
Show JFileChooser
Actual results
"An unrecoverable stack overflow has occurred.
A fatal error has been detected by the Java Runtime Environment:
EXCEPTION_STACK_OVERFLOW (0xc00000fd) at pc=0x5e141119, pid=11772, tid=12752
JRE version: OpenJDK Runtime Environment Temurin-17+35 (17.0+35) (build 17+35)
Java VM: OpenJDK Client VM Temurin-17+35 (17+35, mixed mode, emulated-client, serial gc, windows-x86)
Problematic frame:
C [awt.dll+0xd1119]
No core dump will be written. Minidumps are not enabled by default on client versions of Windows
An error report file with more information is saved as:
... \hs_err_pid11772.log
If you would like to submit a bug report, please visit:
https://github.com/adoptium/adoptium-support/issues
The crash happened outside the Java Virtual Machine in native code.
See problematic frame for where to report the bug."
Triaging info
Java version:
OpenJDK Client VM Temurin-17+35 (17+35, mixed mode, emulated-client, serial gc, windows-x86)
What is your operating system and platform?
Windows 10 Enterprise, 19042.1288
How did you install Java?
Installer from Adoptium (MSI)
Did it work before?
Yes. No problem with a jdk-16 or earlier.
Did you test with other Java versions?
Yes. OpenJDK Runtime Environment AdoptOpenJDK-16.0.1+9 (build 16.0.1+9) works fine
The text was updated successfully, but these errors were encountered: