Skip to content
New issue

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

Memory Leak Testing #260

Closed
samreid opened this issue Dec 18, 2018 · 3 comments
Closed

Memory Leak Testing #260

samreid opened this issue Dec 18, 2018 · 3 comments
Assignees

Comments

@samreid
Copy link
Member

samreid commented Dec 18, 2018

Initial reports recorded in #128 (comment)

Today's results over >30 minutes (testing on Mac Chrome in requirejs mode + with ?fuzz)

image

Prior testing and this testing reveals the typical asymptotic behavior, closing.

@samreid samreid self-assigned this Dec 18, 2018
@samreid samreid closed this as completed Dec 18, 2018
@samreid samreid mentioned this issue Dec 18, 2018
@samreid samreid reopened this Jan 6, 2019
@samreid
Copy link
Member Author

samreid commented Jan 6, 2019

Current results over an 8 minute period on requirejs mode, using the analytical mask branch:

image

Reopened to verify memory profile on built version with the branch.

@samreid
Copy link
Member Author

samreid commented Jan 6, 2019

Something must have gone horribly wrong in the recent few commits, or chrome dev tools are acting buggy. These are 5 minutes apart on a built version:

image

@samreid
Copy link
Member Author

samreid commented Jan 6, 2019

After introducing TemporalMasking for #258, I tested 5 minute intervals over 30 minutes and it looked OK, closing:

image

@samreid samreid closed this as completed Jan 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant