[ZBX-12821] Frontend - memory leak in Problems view Created: 2017 Oct 04  Updated: 2018 Apr 25  Resolved: 2018 Apr 23

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F)
Affects Version/s: 3.2.7, 3.2.8, 3.4.2
Fix Version/s: 3.4.9rc1, 4.0.0alpha6, 4.0 (plan)

Type: Problem report Priority: Critical
Reporter: Olegs Vasiljevs (Inactive) Assignee: Miks Kronkalns
Resolution: Fixed Votes: 3
Labels: memoryleak
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Firefox 55.0.3 x86 with 4 tabs of Zabbix 3.4.0 and 3.0.9 daemons/web interfaces.
Firefox 56.0 x86 and Chrome 61.0.3163.100 x64 with 2 tabs each of Zabbix 3.2.7 daemons/web interfaces.


Attachments: PNG File Screenshot2.png     PNG File Screenshot3.png     PNG File Screenshot4.png     PNG File Screenshot5.png     PNG File Selection_152.png     PNG File Selection_204.png    
Issue Links:
Duplicate
Team: Team D
Sprint: Sprint 18, Sprint 19, Sprint 20, Sprint 21, Sprint 22, Sprint 23, Sprint 24, Sprint 25, Sprint 26, Sprint 30, Sprint 31, Sprint 32
Story Points: 5

 Description   

Hello!

It seems a memory leak firstly introduced in ZBX-3988 has become actual for Zabbix web interface versions 3.2.x and 3.4.x. The test for 3.0.x is yet to be carried out.
If browser is left in Problems view for a long enough period (tests have been carried out for 12h and more, but the issue is reproducible on some workstations after as little as 3h), the web interface firstly becomes unresponsive and at later stages even halts execution at default automatic refresh interval.

Expected behavior: workstation's RAM usage is indifferent within a time frame for a selected filtered problems view.

Visible behavior: workstation's RAM usage rises within a time frame for a selected filtered problems view.

Let me know if you will need more information or if you will require additional materials.



 Comments   
Comment by Olegs Vasiljevs (Inactive) [ 2017 Oct 04 ]

In order to reproduce the issue, you have to open 2 and more tabs with Problems view, other types of views are not important.

Here are the tests from SPS-3 (memory usage on Win server with running browsers and more than 1000 problems in Zabbix):

1) Chrome browser and 4 tabs with Problems view in Zabbix 3.2.7:

Memory usage - 90%
Web interface is slow, almost useless

2) Chrome browser and 4 tabs and later 6 tabs with Problems view in Zabbix 3.4.2:

Memory usage - 90%
Web interface is slow, almost useless
More tabs with Problems view = faster increase of memory usage

3) Firefox browser and 4 tabs with Problems view in Zabbix 3.2.7:

Memory usage - 100%
Web interface is useless

4) Firefox browser and Dashboard with Problems widget only and later with 4 tabs with Problems view in Zabbix 3.4.2:

Memory usage - 100%
Web interface is useless
Problems widget is not the cause of the issue.

Conclusion
-Problems view is probably the cause of the issue.
-More tabs with Problems view = faster increase of memory usage.
-Browsers do not always crash but always allocate almost all memory and become slow or unresponsive.

Comment by Miks Kronkalns [ 2017 Nov 22 ]

(1) No translation string changes.

oleg.egorov CLOSED

Comment by Oleg Egorov (Inactive) [ 2017 Dec 12 ]

Main issue was fixed, no frontend crashes.

Comment by Miks Kronkalns [ 2017 Dec 15 ]

I can reproduce the simultaneous crash of all tabs (Chrome) or whole browser (FF) only if externally additional load is generated by some high performance script. This looks more like system crash because it happens always when available memory is critically low and can be reproduced in any Zabbix section.

larisa.grigorjeva can reproduce it also simply leaving browser to work several hours without running additional memory consuming scripts. This is a scenario which should be fixed.

Miks.Kronkalns Without additional externally generated load cannot reproduce. Tried to leave 35 simultaneous tabs opened for 16 hours and they was fully functional at the end.

CANNOT REPRODUCE

Comment by Larisa Grigorjeva [ 2018 Jan 08 ]

Reproduced this bug on newest Firefox 57, Ubuntu 16.
16 opened tabs with Problems page.
Browser crashed after ~20 hours

Comment by orogor [ 2018 Mar 05 ]

Same problems here.
We display alerts on a large screen, we need to restart the computer that drives it periodically.
The browser is frozen and only old alerts are displayed.

Comment by Miks Kronkalns [ 2018 Apr 05 ]

Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-12821

Comment by Miks Kronkalns [ 2018 Apr 23 ]

Fixed in

 - 3.4.9rc1 r80041
 - 4.0.0alpha6 (turnk) r80044

Generated at Fri Mar 29 10:20:36 EET 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.