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

Started a memory viewer, need to add breakpoints #255

Merged
merged 5 commits into from
Feb 16, 2019
Merged

Conversation

torch2424
Copy link
Owner

@torch2424 torch2424 commented Feb 16, 2019

relates to #226

Started a memory viewer, and abstracted all of the virtual list type code stuff. Also, found a huge memory issue in relaying messages, and getting an infinite message listening for our smart workers.

This PR is only half done. but merging now because the between-refresh memory leak is bothering me 😠

screen shot 2019-02-15 at 9 51 31 pm

@torch2424 torch2424 self-assigned this Feb 16, 2019
@torch2424 torch2424 merged commit e8ee229 into master Feb 16, 2019
@torch2424
Copy link
Owner Author

So I found out the big memory leak is caused by the import { WasmBoyLib } from './wasmboy/wasmboy'; and the from './debug/debug' imports in lib/index.js.

If you comment those out, and export an empty object. no more leak between refresh 😄

@torch2424 torch2424 deleted the memory-viewer branch February 16, 2019 08:07
@torch2424
Copy link
Owner Author

Sorry but gonna use this to track memory leak.

So it seems like it may have something to do with lib/audio files. But since the leak didn't start until: #228

Going to assume it has something to do with how we are passing around WasmBoy.

@torch2424
Copy link
Owner Author

Found the memory leak:

https://github.com/torch2424/wasmboy/blob/master/lib/wasmboy/wasmboy.js#L38

Seems like chrome doesn't like firing off promises on the visibility events 😎

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

Successfully merging this pull request may close these issues.

1 participant