The turned off JEMALLOC seems to cause problems

[Nicholas A. Zigarovich]

Mike Hommey wrote:
> On Tue, Feb 10, 2009 at 01:52:22PM -0800, David Spreen wrote:
>   
>> Axel Beckert <abe at deuxchevaux.org> writes:
>>
>>     
>>> In the #conkeror IRC channel we currently have the problem that for
>>> two people running conkeror on Sid (i386 and amd64) conkeror freezes
>>> quite often -- even on the starting paged, so it's close to being
>>> reproducable -- if and only if MOZILLA_NO_JEMALLOC is set to 1 as it's
>>> done by default in Debian's xulrunner-1.9 since 1.9.0.3-1. Setting
>>> MOZILLA_NO_JEMALLOC=0 solves the problem.
>>>       
>> It doesn't really freeze. It drives the CPU usage to 80-100% and
>> therefore has a tremendous impact on system performance. Conkeror keeps
>> responding but obviously very slowly.
>>
>>     
>>> It happens with both current upstream version from git as well as with
>>> the version in Lenny/Sid.
>>>
>>> OTOH neither me nor another Debian Lenny user can reproduce these
>>> problems at all. I use Conkeror daily on Lenny i386/amd64 and every
>>> few days also on Sid i386/amd64 since months without such problems.
>>>       
>> I think this assessment is a little premature. We don't know if there
>> Lenny users out there that can reproduce the problem. It is of course
>> possible that it's a sid specific issue but given that there are people 
>> unable to reproduce it on sid, I think it's more likely that both
>> distributions are affected.
>>
>> I have had this problem ever since September, when JEMALLOC was globally
>> disabled with the upload of 1.9.0.3-1. 
>>     
>
> What about when setting MOZILLA_DISABLE_PLUGINS=1 ? Maybe one of the
> plugins particularly feels better with jemalloc ?
>
> Mike
>   

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.

Cheers,

- Nick