On 26/04/2015 18:56, Lemon Juice wrote:
> On 2015-04-26 10:01, Mason83 wrote:
>> On 26/04/2015 09:49, Mason83 wrote:
>>
>>> For a long time (going back at least 9 months to SM 2.29)
>>> Seamonkey crashes when compacting IMAP folders.
>>>
>>> Earlier reports:
>>>
>>>    Date: Tue, 16 Dec 2014 18:21:56 +0100
>>>    Subject: SM 2.31 still crashing when compacting IMAP folders
>>>    Message-ID: <[email protected]>
>>>
>>>    Date: Sat, 04 Oct 2014 10:21:29 +0200
>>>    Subject: SM 2.29.1 crashes when compating some IMAP folders
>>>    Message-ID: <[email protected]>
>>>
>>> Are you aware of an open bug?
>>> (I'll open one, please dup if necessary.)
>>>
>>> Not only is this a crasher, but it leaves the mailbox in
>>> a corrupt state.
>>>
>>> Could it be Seamonkey only? Or is Thunderbird also affected?
>>
>> Might be related to Bug 1066998
>> Email compact folders skews titles from bodies in list, mismatch (crashes 
>> reported)
>> https://bugzilla.mozilla.org/show_bug.cgi?id=1066998
>>
>> Although my crash signature is different.
> 
> If you are not sure if your crash has the same origin as bug 1066998 
> then try the workaround for compacting folders as presented at the top 
> of that bug page - if it works for you then most probably it's the same. 
> I suspect there may be multiple crash signatures possible here.
> 
> It looks like the bug is too obscure/difficult for the developers to 
> deal with at the moment. But reading from bug 1066998 this should be 
> automatically fixed when Thunderbird 38 is released with the new cache 
> system, which apparently is to blame for these crashes. This would 
> translate to SeaMonkey 2.35.

In about:config, I saw browser.cache.use_new_backend
which comes with the following comment:

Preference for switching the cache backend, can be changed
freely at runtime
0 - use the old (Darin's) cache
1 - use the new cache back-end (cache v2)

The default is 0, and I set it to 1.

I was then able to compact my 8 IMAP accounts without crashing.

BTW, how is Thunderbird 38 going to fix the problem?
By switching to the new cache back-end?

Regards.

_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to