[SOLVED] Re: The turned off JEMALLOC seems to cause problems

[Axel Beckert]

Hi,

JFYI:

In the meanwhile we found a fix to that 100% CPU problem in conkeror.

On Sun, Mar 01, 2009 at 02:46:52PM +0100, Axel Beckert wrote:
> On Thu, Feb 12, 2009 at 10:57:26AM -0500, Nicholas A. Zigarovich wrote:
> > It happens for me when MOZILLA_NO_JEMALLOC=1 and 
> > MOZILLA_DISABLE_PLUGINS=1. Conkeror immediately eats 70% of my CPU while 
> > sitting at about:blank.
> > 
> > The problem disappears when MOZILLA_NO_JEMALLOC=0.
> 
> In the meanwhile, this doesn't seem to help anymore either for Nick.
> AFAIK he now has that problem independently of MOZILLA_NO_JEMALLOC. (Not
> sure about other users yet, though.)

We still don't know the correlation between MOZILLA_NO_JEMALLOC and
the 100% CPU problem, but setting places.frecency.updateIdleTime to 0
solved the issue since conkeror doesn't use the from time to time
automatically computed frecency values.

Problem was IIRC that although this value is set quite high by
default, the calculations have been started every (less than a)
second for whatever reason.

The problem has been fixed upstream in
http://repo.or.cz/w/conkeror.git?a=commitdiff;h=c92814d3c8b72f70e7a0b3fe1708d7c8c275977b
and will be fixed in unstable with the next upload, too.

The problem hasn't appeared anymore since that fix has been committed
about a week ago.

		Regards, Axel
-- 
Axel Beckert - abe at deuxchevaux.org, abe at noone.org - http://noone.org/abe/