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

Potential memory leak in the 'jzz' module #432

Open
djipco opened this issue Sep 17, 2024 Discussed in #426 · 1 comment
Open

Potential memory leak in the 'jzz' module #432

djipco opened this issue Sep 17, 2024 Discussed in #426 · 1 comment
Assignees
Labels
Type: dependency Issue that cannot be resolved until a dependency is fixed

Comments

@djipco
Copy link
Owner

djipco commented Sep 17, 2024

Discussed in #426

Originally posted by briansin August 5, 2024
whoa, so just found a bigger problem with either WebMidi/jzz, so haven't
even gotten around to debuggin why enable takes so long. Let's say I make
a call to WebMidi.enable() and then do absolutely nothing else with WebMidi
for the entire process (process has an express server, so basically stays
runnign all the time). There is some crazy memory leak in the underlying
library such that it ate through 64 GB of memory in about 2 days....
literaly calling enable() and then doing absolutely nothing else.

Thoughts?

Thanks

@djipco djipco self-assigned this Sep 17, 2024
@djipco
Copy link
Owner Author

djipco commented Sep 17, 2024

Issue created on the jzz repo.

@djipco djipco changed the title Potential Memory Leak in the JZZ Module Potential memory leak in the 'jzz' module Sep 17, 2024
@djipco djipco added the Type: dependency Issue that cannot be resolved until a dependency is fixed label Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: dependency Issue that cannot be resolved until a dependency is fixed
Projects
None yet
Development

No branches or pull requests

1 participant