SAPMachine process exits silently when AWT method GraphicsEnvironment.getDefaultScreenDevice() is called

[konstantin-schwed]

Hi colleagues,

We face an issue that in our application the JVM process just exits without any dump, we just see only this on the console:

Process finished with exit code -1073740791 (0xC0000409)

We have tracked the execution down to the following code. There it just exits:

sun.awt.Win32GraphicsEnvironment.getDefaultScreenDevice(Win32GraphicsEnvironment.java:106)
org.pushingpixels.substance.internal.utils.SubstanceCoreUtilities.getBlankImage(SubstanceCoreUtilities.java:624)
org.pushingpixels.substance.internal.utils.NoiseFactory.getNoiseImage(NoiseFactory.java:76)
org.pushingpixels.substance.api.painter.decoration.MarbleNoiseDecorationPainter.(MarbleNoiseDecorationPainter.java:53)
com.sap.nw.performance.supa. ***

We run on Windows 11 and use SapMachine 21.0.10+7-LTS

The problem only happens when

• You run the application from IntelliJ (just "run" or "debug", same thing)
• You use multiple monitors with "extend desktop"
• You run on one of 2 laptops in our team
• You run in the runtime environment of our application (classpath, etc.)

Long list of things we have tried so far that didn't help

• Update the version of the org.pushingpixels.substance libraries
• Clean local repo in .m2 and build everything from scratch
• Update the JVM (currently Sap Machine 21.0.10+7-LTS)
• Numerous restarts
• Update the NVIDIA video card driver
• Update the INTEL video card driver
• Downgrading IntelliJ to 2024.3.7

You're welcome to contact me (Konstantin Schwed) for further details. We track the issue for us in the ticket TDPT-4954 in the corporate JIRA.
Regards, Konstantin

[MBaesken]

Could it be that you get no screen devices in your setup and then run into an AWTError ?

https://github.com/openjdk/jdk21u-dev/blob/747e02e4eea4c6330534fdb2f3fb5b8cafb9d66c/src/java.desktop/windows/classes/sun/awt/Win32GraphicsEnvironment.java#L105

Other explanation might be that the crash/exit happens in getScreenDevices() itself.

[MBaesken]

Btw is the issue present also in higher JDK versions line SapMachine25 ?

[konstantin-schwed]

@MBaesken Thank you,

1. The same issue happens when running on Sapmachine 25.0.2

2. The last line I am able to debug is this one.

After that I am not able to enter the D3DGraphicsDevice.createDevice() method with debugger, the process exits here.

Here is the full stack trace
at sun.awt.Win32GraphicsEnvironment.makeScreenDevice(Win32GraphicsEnvironment.java:211)
at sun.java2d.SunGraphicsEnvironment.getScreenDevices(SunGraphicsEnvironment.java:83)
at sun.awt.Win32GraphicsEnvironment.getDefaultScreenDevice(Win32GraphicsEnvironment.java:96)
at org.pushingpixels.substance.internal.utils.SubstanceCoreUtilities.getBlankImage(SubstanceCoreUtilities.java:601)
at org.pushingpixels.substance.internal.utils.NoiseFactory.getNoiseImage(NoiseFactory.java:78)
at org.pushingpixels.substance.api.painter.decoration.MarbleNoiseDecorationPainter.(MarbleNoiseDecorationPainter.java:53)
at com.sap.*** **

[MBaesken]

From the stack trace and coding you show, it might be an issue with Direct3D. Here https://docs.oracle.com/javase/8/docs/technotes/guides/2d/flags.html the system property -Dsun.java2d.d3d=false is mentioned to disable D3D, does this make a difference on your setup ?

Btw. did you find some hserr file in the meantime (in case it really is a crash) ?