HD Install :: Memory Leak

I should have been aware of that curaga, thanks. I've already downloaded all the WMs from myDSL, I'll put them on my todo list.

Well, that's two days now and the memory use with fluxbox and XVesa.tar.gz has not changed at all:

Code Sample

$watch -n 60 pmap 11707 | grep -w total
total 16904K
total 16904K
...
total 16904K

- so maybe the problem is cured in the kdrive from Xfree-4.6...

Edit: spoke too soon, now after surfing the web for a while, opening some new tabs in firefox, etc the memory leak has started up again.

I have had occasions where ram use has maxed unexpectedly (fluxbox + xvesa) - I'd never read about this memory leak issue, so now I know.

Quote

JWM is dressed up in very crude gray boxes.

I agree that jwm has a spidery look, which is a real pity. Is there a way of improving this I wonder? Would dfferent gtk+ theming make any difference, or has that got nothing to do with it?

john.martzouco:

Quote

JWM is dressed up in very crude gray boxes. I also dislike the mini icons next to all of the commands....I also very much like that double-clicking the caption bar in FB shades the window. This is a new feature for a guy from the Windows world, but it's sooooo much more intelligent than minimizing to a taskbar.

The colors can be adjusted to suit your tastes in .jwmrc, and you can remove the icon tags there as well if you don't want icons. Most of the color settings can be gradients (two colors separated by a colon); the menu and text colors are one color. JWM also allows shading of windows by scrolling your mouse over the window title bar or via keystroke (the default config uses alt-F2 for window menu options; you can configure in your own keystrokes as well -- I use Ctrl-s to shade/unshade).

I disagree that Windows users don't want a similar interface when they switch to Linux. One of the reasons Linux has been able to win over Windows users is because the most common interfaces -- Gnome, KDE -- are very Windows-like. JWM, IceWM, etc., work on common principles that are intuitive for most people: one button for a menu, a taskbar to show what's running and iconified applications, and maybe a clock. Familiarity causes people to say, "I understand this." Less familiarity means (sometimes) more learning curve, and that's beyond the comfort zone of most people.

WDef:

Quote

Would dfferent gtk+ theming make any difference, or has that got nothing to do with it?

I don't think that matters as much as color selection. I've played around with configuring JWM the last couple weeks (trying to make it more keyboard-friendly before going back to ratpoison on my laptop and hacking a lua-console menu system) and find that it looks better the more contrast there is between gradient colors where they're allowed (which is everywhere except the default menu background). I last had JWM looking kind of like the blueglass theme for fluxbox with a cyan/grey gradient and white letters for active over a medium grey menu background and black letters on the menu.

Quote (Juanito @ Nov. 29 2007,20:41)

Well, that's two days now and the memory use with fluxbox and XVesa.tar.gz has not changed at all:

Code Sample

$watch -n 60 pmap 11707 | grep -w total
total 16904K
total 16904K
...
total 16904K

That is not good news. So it appears that fluxbox, even newer ones, and Xvesa, even with a newer version, the issue of a memory leak remains.

Come to think of it, I can't recall any other distribution that is using both fluxbox and Xvesa. Too me, this is a show stopper. I am inclined to remove something that would cause a system failure and therefore possible data loss.

Next Page...
original here.