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
When using GM_xmlhttpRequest, there should not be any memory leaks. We expect Javascript's garbage collector to clean up requests when completed.
Actual Behavior
There is a small memory leak on every call to GM_xmlhttpRequest.
E.g. when GM_xmlhttpRequest is called once every millisecond (to more easily reproduce the bug) then memory consumption climbs by a few megabytes every second.
Initially I thought it might be the lack/presence of handling on* events, but the leak happens either way.
I've also checked if setting the fetch parameter changes the outcome - again, no effect, same outcome.
Specifications
Firefox: 123.0.1 (64-bit)
TM: 5.1.0
OS: Linux Mint 21.3 Virginia
Script
First, run a small webserver locally on port 12300. (Anything goes, it just makes it easier to reproduce the leak locally)
Then, use the following script to reproduce the memory leak:
Expected Behavior
When using
GM_xmlhttpRequest
, there should not be any memory leaks. We expect Javascript's garbage collector to clean up requests when completed.Actual Behavior
There is a small memory leak on every call to
GM_xmlhttpRequest
.E.g. when
GM_xmlhttpRequest
is called once every millisecond (to more easily reproduce the bug) then memory consumption climbs by a few megabytes every second.Initially I thought it might be the lack/presence of handling
on*
events, but the leak happens either way.I've also checked if setting the
fetch
parameter changes the outcome - again, no effect, same outcome.Specifications
Script
First, run a small webserver locally on port 12300. (Anything goes, it just makes it easier to reproduce the leak locally)
Then, use the following script to reproduce the memory leak:
The text was updated successfully, but these errors were encountered: