Bug 15443 - mgaapplet leaks memory
Summary: mgaapplet leaks memory
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: High major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2015-03-07 13:28 CET by Sander Lepik
Modified: 2016-01-04 14:11 CET (History)
5 users (show)

See Also:
Source RPM: mgaonline-3.14-1.mga5.src.rpm
CVE:
Status comment:


Attachments
valgrind's output (489.64 KB, application/x-xz)
2015-03-07 13:29 CET, Sander Lepik
Details

Description Sander Lepik 2015-03-07 13:28:06 CET
Description of problem:
mgaapplet for some reason leaks memory and it leaks a lot.. It was running 1-2 minutes and in that time it reached 328MB then it stopped growing. The first check for updates raised it to 333MB and clicking on the icon added another 6MB (339MB now)


How reproducible:
Not sure if it does it every time but I was able to reproduce it currently on my system.

Steps to Reproduce:
1. Start mgaapplet with this command: valgrind --leak-check=full --show-leak-kinds=all --log-file="mgaapplet.log" mgaapplet

I'll attach the log from valgrind.

Reproducible: 

Steps to Reproduce:
Comment 1 Sander Lepik 2015-03-07 13:29:04 CET
Created attachment 5999 [details]
valgrind's output
Sander Lepik 2015-03-07 13:29:25 CET

CC: (none) => pterjan, thierry.vignaud

Rémi Verschelde 2015-03-11 11:13:01 CET

Priority: Normal => High
CC: (none) => remi
Severity: normal => major

Comment 2 Shlomi Fish 2015-06-05 18:23:15 CEST
(In reply to Sander Lepik from comment #1)
> Created attachment 5999 [details]
> valgrind's output

Does this still happen with latest Mageia 5? MArking as NEEDINFO.

Keywords: (none) => NEEDINFO
CC: (none) => shlomif

Comment 3 Nic Baxter 2016-01-04 05:59:44 CET
Ping

CC: (none) => nic

Comment 4 Shlomi Fish 2016-01-04 11:20:33 CET
(In reply to Nic Baxter from comment #3)
> Ping

Hi Nic! Why are you so terse? What do you want from the reporters of this bug?
Comment 5 Thierry Vignaud 2016-01-04 11:41:37 CET
I fail to reproduce this bug
Comment 6 Nic Baxter 2016-01-04 11:47:41 CET
OK I will try to be more loquacious. I don't mean to be unfriendly, I'm just feeling my way with this stuff and don't want to bother people with lots of words. 


Hi Sander,
Is this still an issue? Please let us know.

Nic
Comment 7 Sander Lepik 2016-01-04 14:11:35 CET
I don't have time to debug it some more And the current memory usage seems OK after one week uptime. So let's close it for now.

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.