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 #12

Open
dronus opened this issue Jun 10, 2022 · 0 comments
Open

Memory leak #12

dronus opened this issue Jun 10, 2022 · 0 comments

Comments

@dronus
Copy link

dronus commented Jun 10, 2022

If creating several instances of DX7() and dropping them, they will leak an object called "WAP", as can be detected with eg. the Chromium Dev Tools Heap Profiler.
As "WAP" holds reference to the whole WebAssembly heap and further objects, this causes an exception in DX7() constructor at some point (some 1000 instances, maybe there is some overall WebAssembly heap limit or something).

Interestingly this even holds true if:
-all DX7 objects are created for the same AudioContext
-they are never connected to any node.
-also holds true for OfflineAudioContext, even if it is never rendered (and thus no AudioNodeProcessor ever is run)

So basically invoking the constructor seems enough to have DX7 leak one instance of WAP forever.

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