[ZBX-5435] Memory leak in a history syncer process Created: 2012 Aug 09  Updated: 2017 May 30  Resolved: 2012 Aug 09

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 2.0.3rc1, 2.1.0
Fix Version/s: 2.0.3rc1, 2.1.0

Type: Incident report Priority: Major
Reporter: Alexey Pustovalov Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: memoryleak
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by ZBX-5763 Memory leak in server Closed

 Description   

The problem appears on a heavy installations.
About 130MB every hour on each history syncer process.



 Comments   
Comment by Alexey Pustovalov [ 2012 Aug 09 ]

Memory not freed:
-----------------
Address Size Caller
0x000000000164df00 0x9 at 0x7f3bdc793462
0x000000000164f050 0x4000 at 0x7f3bdc793462
0x0000000001653060 0x2007 at 0x7f3bdc793462
0x0000000001655290 0x7 at 0x448699
0x00000000016552b0 0x7 at 0x448699
It repeats 427918 for about 1 hour.

Comment by Andris Mednis [ 2012 Aug 09 ]

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

Comment by Oleksii Zagorskyi [ 2012 Aug 10 ]

Why it's not described when this leak can appear ?
Ne need this information described here.

Comment by Alexander Vladishev [ 2012 Aug 10 ]

Memory leak occurred in three cases:
1. in processing of trigger expressions by history syncers
2. in processing of trigger expressions by a timer process
3. in processing of a "

{TRIGGER.EXPRESSION}

" macro by a escalator process

Comment by Alexander Vladishev [ 2012 Aug 10 ]

Great work! Successfully tested!

Comment by Andris Mednis [ 2012 Aug 10 ]

Fixed in versions pre-2.0.3 rev. 29535 and pre-2.1.0 rev. 29537.

Comment by Oleksii Zagorskyi [ 2012 Oct 30 ]

Here no any words that the leak related to libssh2, but Rich in another issue report ZBX-5763 mentioned that and he described that the leak has been fixed here.

If it's truth then it's sad it was not described here

Comment by richlv [ 2012 Oct 30 ]

no, i meant that libssh2 leak was discovered in another issue, but this issue fixed another leak. i just mentioned all known memleaks a person should be aware of

Comment by Oleksii Zagorskyi [ 2012 Oct 30 ]

But you mentioned there (in ZBX-5763) two identical issue numbers and they both are current issue ZBX-5435

Maybe you in 2nd place you wanted to mention another ZBX-4602 ?

Comment by richlv [ 2012 Oct 30 ]

duh, thanks. fixed the link

Comment by Oleksii Zagorskyi [ 2012 Oct 30 ]

Nice, discussion is closed.
To all - ignore please our today's conversation here.

Generated at Fri Apr 26 10:50:09 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.