Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Investigation memory allocations #2440

Closed
ericproulx opened this issue May 18, 2024 · 1 comment · Fixed by #2441
Closed

Investigation memory allocations #2440

ericproulx opened this issue May 18, 2024 · 1 comment · Fixed by #2441
Labels

Comments

@ericproulx
Copy link
Contributor

ericproulx commented May 18, 2024

@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

@dblock
Copy link
Member

dblock commented May 20, 2024

If you don't mind, I would like to investigate before releasing it to find the culprit.

Absolutely. Bisect it?

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

Successfully merging a pull request may close this issue.

2 participants