Bugzilla – Bug 4378
SlimServer / SN web page: memory leaks, increased handle usage
Last modified: 2008-12-18 11:12:53 UTC
If leaving the SlimServer page open in the browser (on localhost:9000) over a few hours, the memory and handles consumed by the browser process are extremely large. I first noticed this using Mozilla Firefox (1.5.0.7), and the memory usage has reached 800 MB. Currently, I am using IE 7 RC2 (7.0.5700.6), and the process counts are as follows: - memory usage: 40 MB - VM usage: 560 MB - handles: 43,760
Is this a duplicate of bug 3379? Please check to see if you are running some firefox extensions that may be causing issues.
As described in the original report, this happens regardless of which browser you use. I just tested it using the official version of Internet Explorer 7, and the results are just the same (only 130 MB of memory, and 15,000 handles, but it's only been running for 12 hours.)
I'm not sure what I can do to determine if it's Slimserver's fault that the web browser is consuming too much memory or too many filehandles. Have you mentioned this on the forums to see if anyone there has also noticed this issue? I'll chat with our support staff as well to see if they have any suggestions.
This is likely a javascript memory leak.
(Received today from a customer... ref # 070418-002217) The main problem I'm having is that your software uses a huge amount of memory and handles. slim.exe starts up with over 72 megs of memory! And slimtray.exe starts off with about 1500 handles and in a few days grows to hundreds of thousands! Could you please let me know if you're working on a solution for this? It's slowing my system down tremendously.
I still think this is a case of overblown love of 'ajax' (more commonly known as javascript updates). As SS adds ajax features, you suffer more from browser crap due to computer reloads/hibernate/suspend/hours of updates. aside from that.."too much" mean nothing in terms of a bug summary, as there is no way to target a solution in a objective way. start with that.
I completely understand your point. It is difficult to track down memory leaks, and just as difficult to quantify what excessive memory usage is. As far as reproducing the problem, it is fairly easy to leave the browser running for a couple of days, without any other tabs loaded, and periodically examining the process stats. NB: these stats are not from the SlimServer page, but the squeezenetwork web page, which suffers from the same memory leaks, probably now much worse than SlimServer 6.5.2, which I haven't analyzed in a while, because I don't normally use it. Here are my findings: Image Name PID User Name CPU Memory (P... Handles Description iexplore.exe 244 Galin 00 125,184 K 13,519 Internet Explorer (after 12 hours) iexplore exe 244 Calin 00 167,524 K 27,426 Internet Explorer (after 36 hours) iexplore.exe 244 Calin 00 228,168 K 47,025 Internet Explorer (after 48 hours) 142,288 K 52,497 (over 2 days)
QA to profile several web browsers to understand this issue. It's probably a browser bug, but we should see if there is something we can do to prevent this from happening.
Which browsers should I profile, IE7, firefox, and?
CC'ing Michael, he may have some insight on the issue. Any thoughts, Michael?
Ross: IE6 and 7, Firefox, Safari are the top of the list.
I'd echo Dan's comment #4. Is this still an issue? The report was done for FF 1.5 and MS IE 7 RC2 on SS 6.5.1. There have been quite a few changes since in every component involved.
Calin: Please retest with 7.0 and let us know if the issue remains, and reopen if it's still an issue. Ross: Please also add this kind of profiling to your test setup and also reopen if you see anything.
I profiled IE6, IE7 and Firefox 2.0 here is what I found (7.0 - 16819): Initial observation: IE6 mem 37mb, vm 31mb, handles 549 Firefox 33mb, vm 23mb, handles 192 IE7 47mb, vm 38mb, handles 639 24 hours later: IE6 mem 31mb, vm 40mb, handles 547 Firefox 28mb, vm 40mb, handles 548 IE7 mem 40mb, vm 41mb, handles 620 48 hours: IE6 36mb, vm 47mb, handles 547 Firefox 26mb, vm 26mb, handles 187 IE7 35mb, vm 42mb, handles 599
This bug has recently been fixed in the latest release of SqueezeCenter 7.0.1 Please try that version, if you still see the error, then reopen this bug. To download this version, please navigate to: http://www.slimdevices.com/su_downloads.html