Bug 464040 - [patch] gkrellm leaks 58 bytes per second
[patch] gkrellm leaks 58 bytes per second
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: gkrellm (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Hans de Goede
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-09-25 20:54 EDT by Daniel Colascione
Modified: 2008-10-07 18:38 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-10-07 18:38:41 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
fixes the leak (419 bytes, patch)
2008-09-25 20:54 EDT, Daniel Colascione
no flags Details | Diff

  None (edit)
Description Daniel Colascione 2008-09-25 20:54:41 EDT
Created attachment 317750 [details]
fixes the leak

Description of problem:
gkrellm leaks 58 bytes of memory per second

Version-Release number of selected component (if applicable):
2.3.1-5

How reproducible:
always

Steps to Reproduce:
1. let run gkrellm
2. watch memory use
  
Actual results:
=32341== 13,817,453 bytes in 237,630 blocks are definitely lost in loss record 201 of 201
==32341==    at 0x4006AEE: malloc (vg_replace_malloc.c:207)
==32341==    by 0x9534F3: g_malloc (in /lib/libglib-2.0.so.0.1600.5)
==32341==    by 0x96D4C8: g_strdup (in /lib/libglib-2.0.so.0.1600.5)
==32341==    by 0x80634FA: (within /usr/bin/gkrellm)
==32341==    by 0x8063CB7: (within /usr/bin/gkrellm)


Expected results:
gkrellm shouldn't leak

Additional info:
I run several gkrellms at once. After a while, these gkrellm instances begin to eat hundreds of megabytes.
Comment 1 Hans de Goede 2008-10-07 18:38:41 EDT
Thanks! Patch applied and a new gkrellm has been build for rawhide, some time ago already actually, but appearantly bugzilla ate my comment back then.

Note 2.3.2 is out upstream now so I'll update to that soon.

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