[gentoo-amd64] RAM problem with X

[gentoo-amd64] RAM problem with X

[Luigi Pinna]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi!
Since when xorg 7 became stable, it found some problems with stability 
of my graphic session.
I wrote some times ago but nothing helped to solve this strange 
situation...
The problem is that the X process starts to eat all available memory 
(first RAM and after swap) until that to kill everything (first 
applications and after keyboard and kernel).
Until same days ago all my trials gave no solution.
That was the same with KDE and blackbox graphic environment.
I restarted X server each 5-6 hours and put free memory again (and that 
system worked)
Same 2 days my session run stable without new restart.
I think that a found the problem: firefox-bin.
If I use that program (to use flash website) and I forget it open, X 
process starts to eat the memory; if I close it the problem diseappear 
and very slowly it releases the memory.
Someone notice a similar problem?
It is a bug? Where I must send it? As xorg or firefox-bin bug?
I run a stable system (xorg-7.1).
Each  piece of advice is welcome.
Thanks a lot,
Luigi
- -- 
Public key GPG(0x633F86B7) on hkp://keyserver.linux.it/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFaX2gHmkkjmM/hrcRAq1pAJ91c2l4R3+/Ln6HOEdsiVOFFyQ5WQCffO8h
alZ4jyEkcugDeD+XljwR0Qk=
=G091
-----END PGP SIGNATURE-----
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] RAM problem with X

[Michel Merinoff]

Luigi Pinna wrote:
> Hi!
> Since when xorg 7 became stable, it found some problems with stability
> of my graphic session.
> I wrote some times ago but nothing helped to solve this strange
> situation...
> The problem is that the X process starts to eat all available memory
> (first RAM and after swap) until that to kill everything (first
> applications and after keyboard and kernel).
> Until same days ago all my trials gave no solution.
> That was the same with KDE and blackbox graphic environment.
> I restarted X server each 5-6 hours and put free memory again (and that
> system worked)
> Same 2 days my session run stable without new restart.
> I think that a found the problem: firefox-bin.
> If I use that program (to use flash website) and I forget it open, X
> process starts to eat the memory; if I close it the problem diseappear
> and very slowly it releases the memory.
> Someone notice a similar problem?
> It is a bug? Where I must send it? As xorg or firefox-bin bug?
> I run a stable system (xorg-7.1).
> Each  piece of advice is welcome.
> Thanks a lot,
> Luigi
Yes, this is a problem of firefox in general (why first I wrote
"genetal"?). It exists in windows' firefox, and obviously in *nix. I
reported the problem months ago, and nothing changed.

The problem, as far as I remember, was the firefox blocks pop-up
windows, thus growing in memory until you close it. Check, if there are
any pop-ups in the site causes the problem.
Send instant messages to your online friends http://uk.messenger.yahoo.com 

-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: RAM problem with X

[Duncan]

Luigi Pinna <mailing-gentoo@sailorferris.com> posted
200611261242.24638.mailing-gentoo@sailorferris.com, excerpted below, on 
Sun, 26 Nov 2006 12:42:20 +0100:

> I think that a found the problem: firefox-bin. If I use that program (to
> use flash website) and I forget it open, X process starts to eat the
> memory; if I close it the problem diseappear and very slowly it releases
> the memory.

Unfortunately, firefox isn't known for being the most stable app on the
planet.  There are a lot of folks that use it but can't leave it open for
long periods, or anyway as long as they would if they could, due to they
way it manages/leaks memory.

Unfortunately, flash isn't resource-thrifty either, and being a
source-less binary program, well let's just say it's easy to blame it for
stuff that may or may not be its problem, because it's not open source. 
(As such, it's not going to be on my computer, period, and I'd tend to be
one blaming it, but to be fair, it's easy to blame since it /is/ a black
box we can't see inside of.)  From what I've read, some people find FF's
problems worse when they run flash (just reporting it as I've read it).

So... a couple things that could help, if that is the problem....  One,
get that extension that turns flash embeds into click-links, thereby
avoiding it running unnecessarily.  (I'm a Konqueror fan so don't expect
me to remember the name of the FF extension...)  Two, shut down FF when
you aren't using it.

Of course, I'd /rather/ you simply decided proprietaryware flash wasn't
worth it, but it's your computer and your decision, and not one that I'd
make for you even if I could, as what sort of freedom would I believe in
then. =8^)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: RAM problem with X

[Hemmann, Volker Armin]

On Sunday 26 November 2006 15:15, Duncan wrote:

>

>
> So... a couple things that could help, if that is the problem....  One,
> get that extension that turns flash embeds into click-links, thereby
> avoiding it running unnecessarily.  (I'm a Konqueror fan so don't expect
> me to remember the name of the FF extension...)  Two, shut down FF when
> you aren't using it.
>
> Of course, I'd /rather/ you simply decided proprietaryware flash wasn't
> worth it, but it's your computer and your decision, and not one that I'd
> make for you even if I could, as what sort of freedom would I believe in
> then. =8^)

you can always try mplayer-bin&kmplayer to play (at least older) flash movies 
in konqueror.
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: RAM problem with X

[Luigi Pinna]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alle 15:15, domenica 26 novembre 2006, Duncan ha scritto:
> Unfortunately, firefox isn't known for being the most stable app on
> the planet.  There are a lot of folks that use it but can't leave it
> open for long periods, or anyway as long as they would if they could,
> due to they way it manages/leaks memory.

Yes, I notice it! Sorry that I answer only now but I should do some test 
to be sure about what I'm writing.
As you suggest the problem IS firefox. Normal or bin version do some 
things.
I use firefox the ram goes down fast and I can't rescue it. X process 
uses that memory for a unknown reason and it couldn't release it. I 
didn't notice any change with or without using gtk-engines-qt.
I'll write a bug report to X people because that problem starts with 
xorg 7 release.
Thank you all, you helped me a lot!
Best regards,
Luigi

- -- 
Public key GPG(0x633F86B7) on hkp://keyserver.linux.it/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFdSDrHmkkjmM/hrcRAlR0AJ9gu2OYS0wa92zHwLnSchCGkkfi3wCeNoS8
kVvC0FuJslK0aLdTcqy2vOs=
=LCP3
-----END PGP SIGNATURE-----
-- 
gentoo-amd64@gentoo.org mailing list