iB::Topic::Memory Leak

	Damn Small Linux :: Damn Small Linux Board The DSL Forums

» Welcome Guest
[ Log In :: Register ]

Damn Small Linux Board » Damn Small Linux » HD Install » Memory Leak

		Mini-ITX Boards Sale, Fanless BareBones Mini-ITX, Bootable 1G DSL USBs, 533MHz Fanless PC <-- SALE $200 each!
		Get The Official Damn Small Linux Book. DSL Market , Great VPS hosting provided by Tektonic

Pages: (7) </ ... 2 3 4 5 6 [7] >/

[ Track this topic :: Email this topic :: Print this topic ]

Topic: Memory Leak, How to find it

< Next Oldest | Next Newest >

Juanito

Group: Members
Posts: 1601
Joined: Sep. 2005

Posted: Dec. 09 2007,14:16

I tried a similar test with jwm, firefox and Xvesa from the base dsl using dsl-3.4.2:

Code Sample

$ watch -n 60 pmap 15676 | grep -w total
total 14460K [00d 22h 30m]
total 20600K [open firefox 4 tabs browser.cache.memory.capacity 8192]
total 20584K [00d 22h 36m]
total 21532K [00d 23h 12m]
total 21764K [00d 23h 27m]

If I don't touch the machine, I can sit and watch the memory used click up by 4 or 8KB most minutes (I assume the "60" in the watch command is 60s).

Am I missing something here?

roberts

Group: Members
Posts: 4983
Joined: Oct. 2003

Posted: Dec. 09 2007,17:03

The original tests (old thread) did not include Firefox.

Juanito

Group: Members
Posts: 1601
Joined: Sep. 2005

Posted: Dec. 10 2007,03:23

Somehow I missed that...

Closing firefox stopped the memory leak with jwm straight away. I restarted with fluxbox - running "top" in one window and running the "watch" command on Xvesa in another - left it running overnight and there was no leak without firefox.

This last part seems to contradict the original thread and points to firefox as being the cause of the problem with both fluxbox and jwm.

roberts

Group: Members
Posts: 4983
Joined: Oct. 2003

Posted: Dec. 10 2007,22:12

With all the internal changes to DSL over the last two years, the question remains, "Can the test of Dec 2005" be reproduced?

To be fair, one would have to use DSL v3.4.x and boot with with base, norestore, and legacy options. Then proceed as was posted back on 12/13/2005, i.e., top and three xterms containing the "watch".

chaostic

Group: Members
Posts: 328
Joined: Mar. 2005

Posted: June 25 2008,05:38

Edit: Err. Ignore this. I just read it back and it sounds a bit daffy even to me...
Edit: Aside from daffy, it doesn't work either. My xvesa usage doubled again in 24 hours, even without having launched xmms from inside of fluxbox.

Bringing this back up because I have a bit of insight in what may be part of the leak (DSL 3.4.11, fluxbox, xvesa, 6 and a half days uptime). Within about 3 hours, my xvesa jumped from 13mb to 30mb, going up 4kb per second when I noticed it. Only x app I was running was xmms. When I killed xmms, the xvesa memory usage went down .5mb. I have since started xmms again, but from a ssh session (I set the DISPLAY variable).

Anyway, the insight is, could it be that the memory leak is caused in xvesa only when a program is launched from fluxbox?

34 replies since Nov. 27 2007,15:43

< Next Oldest | Next Newest >

[ Track this topic :: Email this topic :: Print this topic ]

Pages: (7) </ ... 2 3 4 5 6 [7] >/

Damn Small Linux Board » Damn Small Linux » HD Install » Memory Leak