You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: