Closed
Bug 306513
Opened 19 years ago
Closed 19 years ago
crash when adding a new event
Categories
(Calendar :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: jminta, Assigned: mostafah)
Details
Attachments
(2 files)
For very small size calendars, this doesn't seem to happen. However, as I've been beginning to use trunk Sunbird more for actual data, I've been noticing this crash more and more. It always seems to happen after clicking 'OK' in the new event dialog. After restart, the event I was attempting to create does appear. Nominating for blocking 0.3a1, but I'd rather someone who knows more about what the stack actually means, etc. decide.
| Reporter | ||
Comment 1•19 years ago
|
||
Updated•19 years ago
|
Attachment #194397 -
Attachment mime type: application/octet-stream → text/plain
| Reporter | ||
Comment 2•19 years ago
|
||
This one has a #0, and also includes p aContent and p *aContent I have a suspicion the crash may be related to the fact that I have a mouseover preview for an event that stays up even when the event dialog is open.
| Reporter | ||
Comment 3•19 years ago
|
||
Confirmed reproduction steps: 1.) Get a somewhat slow computer. 2.) Double click on a day to create a new event. 3.) Before the event dialog opens, move the mouse over an event and leave it there until the event dialog opens. 4.) When the event dialog comes up, observe that the mouseover preview for the event appears on top of the dialog. 5.) At this point you should be guaranteed a crash of some kind once you hit 'OK' in the dialog. Depending on what you do or do not mouseover (other events around the dialog, the mouseover preview itself, etc), the stack changes. One time I managed to get WARNING: NS_ENSURE_TRUE(aFrame) failed, file /home/joey/mozhack/mozilla/layout/xul/base/src/nsMenuPopupFrame.cpp, line 743 before the crash.
| Reporter | ||
Comment 4•19 years ago
|
||
I can't seem to make this happen anymore. -> WFM.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•