-
-
Notifications
You must be signed in to change notification settings - Fork 122
Open
Labels
Context: Node.jsProblem specific to Node.jsProblem specific to Node.jsType: dependencyIssue that cannot be resolved until a dependency is fixedIssue that cannot be resolved until a dependency is fixed
Description
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
Metadata
Metadata
Assignees
Labels
Context: Node.jsProblem specific to Node.jsProblem specific to Node.jsType: dependencyIssue that cannot be resolved until a dependency is fixedIssue that cannot be resolved until a dependency is fixed