Skip to content
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

(fix) Add check to cleanup for active FX Application Thread. #288

Merged
merged 2 commits into from Jun 30, 2016

Conversation

Ortner
Copy link
Contributor

@Ortner Ortner commented May 27, 2016

Issue

see #287 and #247

Solution

Added method isFXApplicationThreadRunning() in FxToolkit to detect whether FX Application Thread is running. Clean up code is only pushed on the FX-Thread if it is running.

fixes #287
fixes #247

Jan Ortner added 2 commits May 27, 2016 17:03
Task-Url: http://github.com/TestFX/TestFX/issues/issue/287

Added method to detect whether FX Application Thread is running. Clean
up code is only pushed  on the FX-Thread if it is running.

fixes TestFX#287
fixes TestFX#247
Task-Url: http://github.com/TestFX/TestFX/issues/issue/287

Removed extra method waitForCleanup. Query isFXApplicationThreadRunning
directly from the cleanup method, so nothing gets called. Throw
TimeoutException if not running.
@Ortner
Copy link
Contributor Author

Ortner commented May 27, 2016

Modified the solution a bit:
Direct call to isFXApplicationThreadRunning() from cleanupApplication, service.cleanupApplication(application) doesn't get called at all.

TimeoutException will be thrown if FX Application Thread is not running. This may better match the current behaviour if stuck.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

(bug) Cleanup hangs when FX Application Thread got killed Platform.exit()
2 participants