http://bugzilla.novell.com/show_bug.cgi?id=503151 User wolfgang@rosenauer.org added comment http://bugzilla.novell.com/show_bug.cgi?id=503151#c13 --- Comment #13 from Wolfgang Rosenauer <wolfgang@rosenauer.org> 2009-05-19 10:38:52 MDT --- (In reply to comment #11)
I don't want to argue with you, I'm merely wondering, why isn't it an option? What does the custom malloc() actually do?
Here are some references why mozilla started to use jemalloc as malloc replacement: http://blog.pavlov.net/2008/03/11/firefox-3-memory-usage/ http://blog.pavlov.net/2007/12/04/vlad-and-analysis-of-dtrace-was-used/ http://blog.pavlov.net/2008/02/27/jemalloc-on-trunk-linux-edition/ So it's (probably) not an option because: 1. it helps to keep memory usage under control (at least given the above analysis are correct 2. you never know what can be changed from upstream builds (legally because of their trademark policy) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.