From: Luigi Pinna <mailing-gentoo@sailorferris.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: RAM problem with X
Date: Tue, 5 Dec 2006 08:33:59 +0100 [thread overview]
Message-ID: <200612050834.03989.mailing-gentoo@sailorferris.com> (raw)
In-Reply-To: <ekc7ik$v4k$1@sea.gmane.org>
-----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
prev parent reply other threads:[~2006-12-05 7:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-26 11:42 [gentoo-amd64] RAM problem with X Luigi Pinna
2006-11-26 14:12 ` Michel Merinoff
2006-11-26 14:15 ` [gentoo-amd64] " Duncan
2006-11-26 15:33 ` Hemmann, Volker Armin
2006-12-05 7:33 ` Luigi Pinna [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200612050834.03989.mailing-gentoo@sailorferris.com \
--to=mailing-gentoo@sailorferris.com \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox