Closed Bug 716438 Opened 13 years ago Closed 13 years ago

JS calendar event editing causes very reproducible crash

Categories

(Core :: Widget: Cocoa, defect)

9 Branch
x86
macOS
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 682208

People

(Reporter: ray, Unassigned)

Details

(Keywords: crash)

Crash Data

Attachments

(2 files)

Crash ID: bp-939fd3de-b664-4cc1-be47-b80e32120108
Crash ID: bp-862bfed6-9324-46da-90ca-7f8252120108
Crash ID: bp-706e74fb-a094-4462-8b51-58d7a2120108

I have a page with a bunch of JS that builds a kind of calendar view. It loads with some events included. You can see them in the code in the page.

I can add any number of events and it works fine. I can edit an event and it works fine. But after I do that and click on an event, FF crashes immediately.

FF does not show me the crash stacktrace, so I cannot tell what area of the browser it is in, but I have included the crash ids.

I will include the page source and the JS library (which I put in /Library/WebServer/Documents).
An important detail. If one makes a change to the event and hits the Save button, the crash does not occur. If you enter the description field and hit <return>, this closes the editing window. Then, if you click on another event, FF crashes.

I will report this, also, to the people at dhtmlx.com.
Severity: normal → critical
Crash Signature: Crash ID: bp-939fd3de-b664-4cc1-be47-b80e32120108 → [@ -[ChildView maybeRollup:]]
Component: General → Widget: Cocoa
Keywords: crash
Product: Firefox → Core
QA Contact: general → cocoa
This is probably a dup of bug 682208, which might be fixed in current trunk nightlies.  Please test with today's mozilla-central nightly to find out.

If you can still reproduce with today's mozilla-central nightly, please provide more explicit steps-to-reproduce.  The one's you've given are a bit vague.
Ran on the nightly, specifically "12.0a1 (2012-01-10)", and the crash did not happen.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
For people looking here for:
d2eefdb6f9d4	Nicholas Cameron — Bug 716438; using flags to select a shader. r=Bas

The correct bug is bug 716439.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: