Windows: Add additional launcher to debug jfx problems #2661
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On windows, we are facing different JavaFX-related issues: #2606, #2373, #2610
Since for the normal windows app we do not get any terminal output, also debugging is very difficult, requiring a lot of user cooperation and some skill/support manuals. And since version 1.6.16 the launcher script does not work either, it is impossible to easily get debugging info and analyze (graphical) problems.
This PR alleviates the situation by providing an additional windows launcher (EXE), which logs to the terminal (including stderr!) and enables the javafx debug logging. In the end, the user has to start the debug-launcher and pipe all output to a file and upload the file. No configuration needed, no admin rights needed, minimal user effort.