Tiny Core Linux
Tiny Core Base => TCB Bugs => Topic started by: jur on July 18, 2010, 11:42:25 AM
-
tc 3.0rc1:
I am getting system crashes reliably when using beaver2 to edit script files. I can reliably repeat it by opening a largish text file, say /usr/bin/usbinstall, grabbing the scroll bar and pulling it up and down. After about 10 times response becomes sluggish and soon afterwards it freezes. I can't exit X, I have to do a cold reset by pressing the power button 5s. The last time I was investigating this, .xsession got corrupted.
I am running conky and it does not report the memory getting filled up nor the processor being used beyond the normal.
I did not see this behaviour in tc 2.6.
-
I'll rebuild beaver2 on tc-3 and see if this changes anything.
-
Well well, it's Xvesa that's hogging the ram. It could still be either Beaver or Xvesa that's causing the memory leak, though, perhaps even gtk2 itself.
-
I haven't managed to duplicate the error on tc-3 using Xvesa...
-
..but recompiled version posted anyway
-
Well well, it's Xvesa that's hogging the ram. It could still be either Beaver or Xvesa that's causing the memory leak, though, perhaps even gtk2 itself.
Sorry, I meant to add that I tested and found this behaviour both with Xorg and Xvesa. (Tour de France interfered with my concentrating. :) )
I'll test again tonight. If I have a chance I'll see how the current one does on the work laptop.
-
I tested my work laptop and found the same behaviour, with both beaver2 versions. I was running Xorg.
-
I also found that the reserved ram is freed if beaver is closed before ram runs out. This along with independence of X would point to either beaver or gtk2.
-
I think it is probably beaver because I first noticed it when writing scripts. But I suppose gtk2 is still possible.
I'm not sure about tc 2.x. I never saw it but haven't tested rigorously.
-
I have repeated some tests...
geany with the same dep as beaver2, no problem.
beaver with gtk1 as dep, no problem
beaver2 on tc-2.x, same problem (although I did not have access to 2.x extensions so this test was done with the 3.x extensions)
I guess that tentatively leaves beaver2 as the culprit?
-
..well I can't manage to repeat the error, but it might be good to post a bug report on the beaver site?
-
I suppose misery loves company: I'm so relieved to find I'm not the only one. Using microcore 2.10 with Xorg-7.4 and beaver2 from the 2.x repo. A little editing on a large-ish file will stall the system for ages (or permanently). If I use IceWM, its little system usage meter on the taskbar fills right up and stays that way.
After reading these posts I experimented a little, and found that certain GTK 2 engines make the problem worse, especially Murrine. GTK themes using older, simpler engines like Pixmap, Industrial, or Glide produce a smaller problem, and with a little patience and much pausing, it catches up to itself.
As a side note, with a fellow mini-Linux distro (SliTaz 3.0) on this very same hardware with the same version of Beaver, there's no problem.
-
Just compiled from source, Beaver version 0.4.1 on MicroCore 2.10 Xorg 7.4. No more leak. :D