Date: Mon, 18 Jan 2010 12:25:43 -0800 From: Doug Barton <dougb@FreeBSD.org> To: Oliver Fromme <olli@lurza.secnetix.de> Cc: freebsd-hackers@FreeBSD.ORG, jhs@berklix.com Subject: Re: limits for run away Firefox ? Message-ID: <4B54C3C7.5040904@FreeBSD.org> In-Reply-To: <201001181929.o0IJT5IZ001218@lurza.secnetix.de> References: <201001181929.o0IJT5IZ001218@lurza.secnetix.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/18/10 11:29, Oliver Fromme wrote: > Doug Barton wrote: > > On 01/17/10 17:07, Julian H. Stacey wrote: > > > Hi hackers > > > I'm tired of my X server occasionaly freezing, swap thrasing, & firefox dumps: > > > 4,346,937,344 ~/firefox-bin.core > > > so as a temporary cludge I ran > > > touch ~/firefox-bin.core ; chmod 000 ~/firefox-bin.core > > > > Sorry I don't have a solution to your actual problem, but a better way > > to deal with this is to do: ln -s /dev/null ~/firefox-bin.core > > I think not generating a core dump at all is better than > writing 4 GB to /dev/null. A) The method I proposed is useful for other things too, and as you pointed out it can sometimes be difficult to track down all the ways a given thing is started. B) If we're going to be snarky, it would be far better if it didn't need to dump core in the first place. :) Doug -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ Computers are useless. They can only give you answers. -- Pablo Picasso
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B54C3C7.5040904>