-
Notifications
You must be signed in to change notification settings - Fork 7
[Bug] large memory leak #92
Comments
This is from With a system uptime of 3 days and 23 hours, Chrome has, right now, been running for 3 days and 22 hours. How many days is "a few days"? |
That particular browser session is about 10 days old. I have another 9-day-old session on a different PC where the current consumption is 1,387,040K--on that PC, I've visited mixer to watch a handful of VODs. If you want a more precise timeline, I can note the usage for a while after killing/restarting the extension to get a fresh start. Might also be useful to note that I only really use the extension to get access to theater mode and I'm not logged into a mixer account. Dunno there's some initialization check for an active account that might be leaking that you wouldn't see in your usage? edit: just a quick observation--watching the chrome task manager with no active mixer tabs, I see a small network usage from mixrelixr every ~15s. Memory usage increases every 45s |
Just to be clear, we are looking into this but are not having luck in reproducing the issue. |
In the chrome task manager, I do see network usage from the extension every ~15s. When I was watching it before, the memory footprint would increase consistently with every third network pulse, so every 45s. For whatever reason, it's not consistent as I'm watching it now. Once it took 1m30s to increase, then the next cycle 2m. It could be that I didn't watch it long enough last time before concluding there was a pattern, or maybe it's behaving differently now; sorry, I'm not sure. The memory increase does always occur coincident with a network pulse, but it doesn't happen with every network pulse. This doesn't seem to be impacted by there being mixer tabs open or not. On the PC I was posting usage from above, I don't think there was a mixer tab open at any point during the ~5 days. |
Describe the bug
MixrElixr memory usage continually increases in the background, even if mixer isn't visited at all in a browser session. Have to kill the extension or restart the browser to reclaim the memory.
I very rarely completely close out my browser; after a few days, I find the extension using GB of memory when it hasn't even been active.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Not leak, especially when the plugin isn't in active use.
Screenshots
Environment (please complete the following information):
Additional context
I'm not really sure how to provide more detailed debugging information about a browser extension, but this happens repeatably on multiple PCs for me. So, if you can tell me how to get more useful information, let me know.
The text was updated successfully, but these errors were encountered: