We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
@dblock I've done a memory profile in our stack and somehow next release has a significant higher memory allocation.
Here's the comparison
master
Total allocated: 64160548 bytes (353932 objects) Total retained: 9020245 bytes (26379 objects)
2.0.0
Total allocated: 45345507 bytes (205326 objects) Total retained: 6403149 bytes (14968 objects)
72% more on allocated 76% more retained
If you don't mind, I would like to investigate before releasing it to find the culprit.
Thanks
The text was updated successfully, but these errors were encountered:
Absolutely. Bisect it?
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
@dblock I've done a memory profile in our stack and somehow next release has a significant higher memory allocation.
Here's the comparison
master
2.0.0
72% more on allocated
76% more retained
If you don't mind, I would like to investigate before releasing it to find the culprit.
Thanks
The text was updated successfully, but these errors were encountered: