Force Skiko to 0.8.17 #665
Merged
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
This Skiko version contains an important fix for memory usage. It is more recent than the version used by CMP 1.7.0 (0.8.15), but the CMP team assured us it is a binary-compatible change. As a result you should see greatly decreased memory usage and GC pressure in most scenarios, except when the ComposePanel size changes. That is a more complex fix which will require a number of changes across JBR and Compose, and will come in time.
ghost
approved these changes
Oct 25, 2024
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.
This Skiko version contains an important fix for memory usage. It is more recent than the version used by CMP 1.7.0 (0.8.15), but the CMP team assured us it is a binary-compatible change.
As a result you should see greatly decreased memory usage and GC pressure in most scenarios, except when the ComposePanel size changes. That is a more complex fix which will require a number of changes across JBR and Compose, and will come in time.