From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1GoKpT-0000Q5-9Q for garchives@archives.gentoo.org; Sun, 26 Nov 2006 14:17:59 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.8) with SMTP id kAQEGBSP006007; Sun, 26 Nov 2006 14:16:11 GMT Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by robin.gentoo.org (8.13.8/8.13.8) with ESMTP id kAQEGBSG012745 for ; Sun, 26 Nov 2006 14:16:11 GMT Received: from list by ciao.gmane.org with local (Exim 4.43) id 1GoKnY-0007nn-La for gentoo-amd64@lists.gentoo.org; Sun, 26 Nov 2006 15:16:00 +0100 Received: from ip68-230-97-209.ph.ph.cox.net ([68.230.97.209]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 26 Nov 2006 15:16:00 +0100 Received: from 1i5t5.duncan by ip68-230-97-209.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 26 Nov 2006 15:16:00 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-amd64@lists.gentoo.org From: Duncan <1i5t5.duncan@cox.net> Subject: [gentoo-amd64] Re: RAM problem with X Date: Sun, 26 Nov 2006 14:15:48 +0000 (UTC) Message-ID: References: <200611261242.24638.mailing-gentoo@sailorferris.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: ip68-230-97-209.ph.ph.cox.net User-Agent: pan 0.120 (Plate of Shrimp) Sender: news X-Archives-Salt: f2f2dd2b-1d00-4049-b354-d68c7fcc858b X-Archives-Hash: 874056e8cfffdcb8215662d2c0a1301b Luigi Pinna 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