187713 - xul.mfl corruptions on opening mail filter window, app freeze and 100% CPU

Status: VERIFIED DUPLICATE of bug 169777

(SeaMonkey :: General, defect)

Description

[Mike Coppins]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130

Today I imported all my mail from Eudora 5.1 to Mozilla.  I've been setting up a
lot of filters for a particular account, and mozilla has been restarted a number
of times (the process not hanging around process list) throughout the day.  I
wanted to check a particular filter setup, and when I clicked on 'create message
filters' in the account's 'home page', CPU went to 100% and Mozilla locked up. 
I killed the process and tried again.  Still the same.  I fired up filemon to
see what it was having a problem with, and the file was XUL.MFL.  I deleted it,
restarted Mozilla, and all appears to be well again.  I have kept a copy of the
XUL.MFL file if that would be useful.  The old file is 2.7MB, the new file is 1.5MB.



Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[Mike Coppins]

Sorry, missed a few details:

Reproducible: ALWAYS
If I swap the old (one that caused the hang) XUL.MFL file with the new one, the
same problem occurs.  When I swap them back, it is fine again.

Comment 2

[Snala]

Just a tip. Create a new attachment above and post that file for others to try.

-Snala

Comment 3

[Mike Coppins]

I can't attach the file, it's too big, even zipped, so here's the URL to
download the corrupted XUL.MFL file:

http://lorien.legolas.com/manahmanah/XUL.zip

it'll be uploaded in a couple of minutes.

Comment 4

[Matthias Versen [:Matti]]

it will not work for other ppl because mozilla will possible delete this file
because it's from a different version.


*** This bug has been marked as a duplicate of 169777 ***

Comment 5

[Mike Coppins]

I'm not trying to be irritating by re-opening this bug, but I think it may be a
bit premature to mark it as a duplicate of another bug when the scenario that
led to the hang was different, so there *may* be a different cause.  I just
think over-zealous 'mark as duplicate' actions may result in individual bugs
taking longer to resolve because they appear to have so many depending bug
reports to check.  Also, the cause of the bug which this bug was marked of
hasn't be ascertained yet, so can it be said that the same bug is definitely
causing both scenarios?

Comment 6

[Matthias Versen [:Matti]]

it's excactly the same problem.
You can always reopen this bug if you get this again AFTEr bug 169777  is fixed.


*** This bug has been marked as a duplicate of 169777 ***

Comment 7

[Daniel Wang]

v