Red Hat Bugzilla – Bug 169384
Last modified: 2007-11-30 17:11:14 EST
Description of problem:
zaitcev 3413 26.7 44.9 88980 85880 ? S 01:41 214:43
Version-Release number of selected component (if applicable):
Not on every computer. But where it happens, killing gam_server
does not solve the problem.
Steps to Reproduce:
1. Watch RSS
System runs out of memory.
System does not run out of memory.
Curiously enough, 0.1.6-1 changelog says "memory leak fix".
If anything it made things far worse than before.
Trying 0.1.6-3 now...
I don't see how adding calls to free() can increase memory leaks.
I can't reproduce it, if you do, valgrind 3.0.1 on gam_server
should allow to show said leaks.
Running under valgrind makes gam_server to exit, and it won't keep running now.
I think that perhaps something had an earlier version of libgamin-1.so*.
This is all done without logging out.
only on per user gam_server can run at a given time so if you start
a new one under valgrind it will exit immediately, not valgrind related
unless you have a valgrind older than 3.01
gives informations on how to find what is using gamin and how it is using it
I don't understand what you mean by
"I think that perhaps something had an earlier version of libgamin-1.so*.
This is all done without logging out."
Does this mean that if you log out and in again you don't see the problem ?
Yes, it seems all right now. No problem.
okay, thanks !