Fix memory alloc bug when using trikot-graphql #215
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
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.
Description
The
String.escapeForGraphql()extension function was creating countless String objects inside the "fold" loop.Motivation and Context
In my app, the query was huge, which means that many many String objects were allocated and deallocated about 100ms later, triggering many garbage collecting events. In an older device with low RAM and/or processing power, this could noticeably freeze the UI (in my case, for about 8 seconds!)
How Has This Been Tested?
This fix was tested in my project. We no longer allocate many String objects, instead using a StringBuilder.
Types of changes