[ZBX-3988] Browser memory leak on some pages of zabbix web interface Created: 2011 Jul 28 Updated: 2017 May 30 Resolved: 2011 Dec 20 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Frontend (F) |
Affects Version/s: | 1.8.6, 1.9.6 (beta) |
Fix Version/s: | 1.8.9, 1.9.9 (beta) |
Type: | Incident report | Priority: | Blocker |
Reporter: | Oleksii Zagorskyi | Assignee: | Unassigned |
Resolution: | Fixed | Votes: | 1 |
Labels: | memoryleak | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
WinXP32 SP3, Opera 11.50 build 1074. |
Attachments: | 3operas_memory leak.png Opera_DEV-3988_memleak.png firefox-memory-leak.png |
Description |
Last time (~ last week) i have huge problem - my Opera periodically eats all RAM (4GB), it hangs and if i could not close it in time, even OS hangs and i have only one way - press reset button. I have opened several Zabbix GUI tabs on the Opera all time, and sometimes i leave opened Dashboard tab in the background and i don't select it for some time. After some short time my system becomes unstable and finally not responds - Opera ate all virtual memory. When i switch to tab with Dashboard and move mouse over several widgets (without any click, only mouse over !!!) then Opera drops all memory leak. Speed of memory leak (only one tab with Dashboard opened) ~ 500 Mbytes/hour of virtual memory. I have configured monitoring of revision changes for different components on the my dev-server and i can assume that problem can appears between revs 20500 and 20667. So i think you should to take a look to this situation. And i feel that this situation related to the Another browsers are not tested. |
Comments |
Comment by Oleksii Zagorskyi [ 2011 Jul 28 ] |
Note: Pages Auto-updating is disabled in the profile (Refresh (in seconds)=0) |
Comment by Oleksii Zagorskyi [ 2011 Jul 28 ] |
Meh, just rebooted (by reset button). And I've had opened pages: items.php, trigger_prototypes.php, events.php, tr_status.php |
Comment by Oleksii Zagorskyi [ 2011 Aug 11 ] |
About the picture "3operas_memory leak.png" Other opera instances have ~40-60 tabs opened each. Checked on several different WinXP workstations with the same version of Opera. |
Comment by Aleksandrs Saveljevs [ 2011 Aug 17 ] |
Same happens in Firefox in Zabbix 1.8.6. See firefox-memory-leak.png. The only thing that computer is doing is showing a single slide show on the monitor. |
Comment by richlv [ 2011 Aug 21 ] |
note that slideshow one was reported some time ago already as ZBX-3878 |
Comment by Alexey Fukalov [ 2011 Oct 06 ] |
dev branch: svn://svn.zabbix.com/branches/dev/ZBX-3988 |
Comment by Aleksandrs Saveljevs [ 2011 Oct 06 ] |
Does not seem to leak in Safari, but leaks pretty fast in Internet Explorer 7 and Internet Explorer 9. Also seems to leak slowly in Opera (raised from 130 MB to 190 MB in approximately an hour) on Windows and Firefox and Google Chrome on Linux. |
Comment by Oleksii Zagorskyi [ 2011 Oct 17 ] |
Deep and long tests of this dev branch were made. Memory leak reproducible only on the page "slides.php" (Opera under Linux & Windows). |
Comment by Oleksii Zagorskyi [ 2011 Oct 17 ] |
It seems that memory leaks on the page "slides.php" highly dependent on the screen's (used in the slides) content. |
Comment by Oleksii Zagorskyi [ 2011 Oct 18 ] |
the picture attached. sorry |
Comment by Oleksii Zagorskyi [ 2011 Nov 02 ] |
Maybe it's time to commit this changes to 1.8 branch & trunk ? For slide shows we have separate issue ZBX-3878. |
Comment by Alexey Fukalov [ 2011 Nov 02 ] |
Resolved except slideshow leaks. |
Comment by Aleksandrs Saveljevs [ 2011 Nov 02 ] |
(1) You have added loading of menus.js for items.php and slides.php, but we do not have that JavaScript file in our repository. <asaveljevs> Also, please review r22897. <Vedmak> RESOLVED <asaveljevs> CLOSED |
Comment by Alexey Fukalov [ 2011 Nov 04 ] |
svn://svn.zabbix.com/branches/1.8 22963 |
Comment by Oleksii Zagorskyi [ 2011 Nov 04 ] |
Thank you for fixing ! |
Comment by Oleksii Zagorskyi [ 2011 Nov 23 ] |
I feel that memory leaks are back. Not sure for 1.8 or trunk branch. I need several days to be sure. |
Comment by Oleksii Zagorskyi [ 2011 Nov 23 ] |
Yeah, leaks definitely are back. Currently tested only Dashboard page, but after two days I feel that not only dashboard affected. Related only to trunk branch, i.e. latest revision of 1.8 branch is ok. According to revision changes monitoring (my very specific solution) I suppose the changes between revisions 23287 and 23335 but I'm not sure. <zalex> <Vedmak> Leaks are in Dashboard screen? <zalex> yes, leaks are not only in th dashboard. In the triggers, events pages too. I think in other pages too. <pavels> zalex, when you tested opera, did it leak continuously? I've tried to open about 20 trigger pages simultaneously and it ate up about 20 Mb per refresh, but when it reached 350 Mb the leak seamed to stop and stabilized. I tried it on a different page with just some content and auto refresh, and it seams opera does leak when refreshing a page, but always stabilizes at some point. The trigger page doesn't leak in Firefox or Chrome, the dashboard seems to leak a bit, but much slower. <zalex> pavels, a dynamic of leak in the Opera for windows and linux is different. In windows need to wait ~ 5-10 minutes to see the leaking start. In windows it up every minute and constantly. No need to open many tabs/pages, single page is enough. I always have auto-refresh pages DISABLED, i.e. 0 seconds. <pavels> Wait, you mean that the trigger and event pages leak even when auto refresh is disabled? <zalex> Yes, definitely. All my life (on all zabbix installation, databases, etc) I have auto-refresh pages DISABLED, i.e. 0 seconds. <pavels> Found were the leak is. Now all I need is to figure out how to fix it. |
Comment by Pavels Jelisejevs (Inactive) [ 2011 Dec 20 ] |
Well that was fun and interesting. RESOLVED in /branches/dev/ |
Comment by Oleksii Zagorskyi [ 2011 Dec 20 ] |
Fast test of dev branch shows that the leaks are missing at the events page (Opera for Windows and Linux). <zalex> Report of long testing is ready. NO MORE MEMORY LEAKS !!! Thanks. |
Comment by Alexei Vladishev [ 2011 Dec 22 ] |
It is not about memory leaks, but please also test if blinking works fine without any visible problems in case of large number of visual elements, say, 1000 of triggers with some of them blinking. It is because the new algorithm is more CPU intensive. <pavels> Tested it in firefox with about 700 events, all of them blinking. CPU usage does go up about 10 percentage points, but the page stayed responsive and I haven't noticed any slow downs at all. <zalex> Tested Opera for Windows and Linux with blinking 1000 rows at the events and triggers pages. |
Comment by Pavels Jelisejevs (Inactive) [ 2011 Dec 27 ] |
Merged the jqBlink fix to the trunk r24269. CLOSED. |
Comment by hamid sfandiari [ 2012 Mar 12 ] |
I've same issue on Firefox and chrome .. it's occurs when I used a slide show which contains graph, but when I load a side show with map(s) the problem is not occurs |
Comment by Oleksii Zagorskyi [ 2012 Mar 12 ] |
Hamid, I'd suggest you to move this comment to the ZBX-3878. |