Narasimha-scandGitHub 11f0b6bd51 desktop: show startup errors in a copyable window instead of bare "Failed to launch JVM" (#7261) ...

* desktop: show startup errors in a copyable window instead of bare "Failed to launch JVM"

When any exception escapes main() before the app window appears - a missing
DLL, a failed migration, broken AWT init - the jpackage launcher shows only
"Failed to launch JVM" and the cause is recorded nowhere: the launcher runs
without a console, so stderr is lost. Every report in #4146 stalled on this.

Catch the error and show it in a native Win32 window laid out like a message
box: an error icon and message, two clickable report links (the GitHub issue
tracker and the support email) above a read-only selectable box with the stack
trace, and an OK button. The links are SS_NOTIFY statics opened with
ShellExecute (browser for the URL, mail client for the email). Native, not
Swing, because broken AWT initialization is one of the failure causes. On
Windows the process then exits cleanly so the launcher does not also show its
own box; on other systems the error is rethrown to stderr.

* docs: plan justifying desktop startup error window (#4146)

2026-07-17 15:41:54 +01:00

..

src/jvmMain

desktop: show startup errors in a copyable window instead of bare "Failed to launch JVM" (#7261)

2026-07-17 15:41:54 +01:00

build.gradle.kts

desktop: fix "Failed to launch JVM" on Windows when Java Access Bridge is enabled (one cause of #4146) (#7260)

2026-07-16 13:49:10 +01:00