DIYgod
Done. ff0a9c24cf517378f27b57950469273b15a4e374
This issue has been resolved, so now close
I am reconsidering self-distribution. A Firefox extension reviewer informed me that he couldn't reproduce the same results from our source code on his Ubuntu, leading him to remove the publication...
These problems have been resolved and will be released in the next version, if you still have problems please reopen this issue
Invalid URL errors are fixed in cf15a0a66a6da8576610f8a0331525e542435727, but I'm not sure if it caused the memory leak
I speculate that the memory leak in the v2 version is caused by console.debug. I have removed all console.x at [here](9caee299f5af3293d88dc1c25cce23fd2a444138). Please observe if v2.0.7 still has any memory issues.
In version 2.0.7, the memory consumption is still high, but the background service worker and offscreen.html memory usage seems to be normal. I'm unsure about the exact cause of the...
I further debugged and found that the memory leak may be caused by DOMParser. Then I found a [stackoverflow post]( https://stackoverflow.com/questions/56451731/dom-parser-chrome-extension-memory-leak) confirming my guess, so I removed DOMParser in this...
This issue will be closed because it has been resovled
Firefox does not allow extensions to use eval, so Firefox's remote rule updates are disabled, this is not a thing we can fix, so this issue will be closed.