Closed Bug 25948 Opened 26 years ago Closed 26 years ago

Crash doing an 'Edit page' or bringing up compose window

Categories

(SeaMonkey :: General, defect, P3)

PowerPC
Mac System 8.5
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: sfraser_bugs, Assigned: sfraser_bugs)

References

Details

(Keywords: crash)

We're seeing occasional crashes bringing up the compose window from the taskbar, or doing an Edit Page. The crash does not happen every time, and seems sensitive to timing, and which memory allocators are being used. It has the hallmarks of a heap corruption bug, or perhaps stack overflow.
Something else i should add; in this situation, the composer window comes up blank.
Bug 25962 exists to describe the blank composer window issue. That might be related to this crash.
This bug smells very similar to 25695, which is the same kind of problem, but on the preferences dialog.
m14 since this is a crasher
Target Milestone: M14
This is almost certainly related to bug 6553.
Status: NEW → ASSIGNED
Depends on: 6553
I can't reproduce this problem in the January 28 build but I can in the January 29 build.
Now that I backed out the change in 6553, this bug should be fixed.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Adding crash keyword
Keywords: crash
*spam* changing qa contact from nobody@mozilla.org to me (BlakeR1234@aol.com) on 121 open or resolved (but not verified) bugs. sorry for the spam everybody, but most of these bugs would just remain dormant and not checked by QA otherwise. I'm not sure how so many bugs have nobody as their QA contact, but I suspect this is the fault of some sort of bugzilla corruption that happened at some point (most of these bugs are in the 20000-26000 range, and I don't see where in the activity log that QA contact explicitly changed to nobody@mozilla.org) Anyways, sorry again for spam. If you really get annoyed, I'm usually available in #mozilla on IRC for torture.
QA Contact: nobody → BlakeR1234
Verified Fixed: - MacOS 9.0 2000082108
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.