Dispose SwingInteropContainer after closing the scene
#2277
Conversation
This file contains hidden or 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
MatkovIvan
approved these changes
Aug 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
In
ComposeSceneMediator.dispose(), we currently call (swing)interopContainer.dispose()before disposing the scene, but disposing the scene schedules calls for the interop container, which are then never executed because the mediator is already disposed.Fixes https://youtrack.jetbrains.com/issue/CMP-8679/ComposePanel-doesnt-remove-interop-components-on-own-removal
Testing
Added a unit test
Release Notes
Fixes - Desktop
SwingPanelchildren ofComposePanel, when the compose panel is itself removed from the hierarchy.