Date: Sun, 15 Mar 2009 19:25:38 +0100 From: cpghost <cpghost@cordula.ws> To: Kris Kennaway <kris@FreeBSD.org> Cc: freebsd-questions@freebsd.org Subject: Re: Speeding up exit(2)? Message-ID: <20090315182538.GA1375@phenom.cordula.ws> In-Reply-To: <49BD419B.1040608@FreeBSD.org> References: <20090315120024.E004210656DB@hub.freebsd.org> <20090316023903.T95588@sola.nimnet.asn.au> <alpine.BSF.2.00.0903151853420.42002@wojtek.tensor.gdynia.pl> <49BD419B.1040608@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Mar 15, 2009 at 05:57:47PM +0000, Kris Kennaway wrote: > Wojciech Puchar wrote: > >> By this stage mozilla is about 150MB with about 60MB resident, and swap > >> is pushing 200MB. *seriously* paging, just on flipping to another tab. > >> Now close mozilla and watch top while it's shutting down. Go and pour > >> yourself a cuppa, there's no hurry .. > > > > just tested with opera - the same. crappy software rulez ;) > > Yes, clearly web browsers should be optimized for speed of exiting. That's correct. Normally systematic freeing of resources is one of the best ways to prevent memory leaks in long running programs, so it can't be too bad to free/delete all malloc-ed/new-ed chunks upon exit. But here, the opposite may be better: there should be a faster way to exit, bypassing all manual and automatic cleaners. But that's up to every single program and not OS'es business. Thanks again for all the insight. > Kris -cpghost. -- Cordula's Web. http://www.cordula.ws/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090315182538.GA1375>