Just a heads up. Don't update Seamonkey Nightly beyond yesterday 08-29 if you have an IMAP account defined. Seamonkey will not start and the Crashreporter will be shown. This also affects Thunderbird Nightly and is tracked in bug 1299116 (not open to the public). A new check was added to the Mozilla source code and this is the result. Even if you do not have an IMAP account it may still crash because until the first bug is fixed any possible others remain undetected.

The good news. Once its fixed some random crashes will no longer occur because actually the Thunderbird and Seamonkey shared source code is at fault.

As another twist for tomorrow's nightly build, migration to the new cache "version 2" has checked in today with bug 1021843, where actually enabling it for SeaMonkey will be covered in bug 1241622. It appears that versions 1 (which is used thus far) and version 2 (new) can be used in parallel right now, but now clue if there are any effects from that migration on using IMAP and NNTP (news) accounts with the old version 1 cache.

frg wrote:Just a heads up. Don't update Seamonkey Nightly beyond yesterday 08-29 if you have an IMAP account defined. Seamonkey will not start and the Crashreporter will be shown. This also affects Thunderbird Nightly and is tracked in bug 1299116 (not open to the public).

rsx11m wrote:It appears that versions 1 (which is used thus far) and version 2 (new) can be used in parallel right now, but now clue if there are any effects from that migration on using IMAP and NNTP (news) accounts with the old version 1 cache.

According to JorgK, the MailNews changes made won't work with cache 1, so this is effectively another bustage until Bug 1241622 checks in (or just disable the cache when using Mail & News).