Closed
Bug 794212
Opened 12 years ago
Closed 12 years ago
Debug build: Assertion failure and crash when starting drag and drop in calendar view
Categories
(Calendar :: Calendar Frontend, defect)
Calendar
Calendar Frontend
Tracking
(Not tracked)
RESOLVED
FIXED
1.9
People
(Reporter: ssitter, Assigned: ssitter)
Details
Attachments
(1 file)
4.11 KB,
patch
|
Fallen
:
review+
Fallen
:
approval-calendar-beta+
|
Details | Diff | Splinter Review |
Starting an event drag and drop operation in calendar view of a Debug build asserts and the application crashes.
> Assertion failure: mInitialized, at .../src/mozilla/widget/xpwidgets/nsTransferable.cpp:447
Reason is that init() of the nsITransferable object has not be called.
Assignee | ||
Comment 1•12 years ago
|
||
Add missing calls to init(). I'd say we don't care about Private Browsing mode and therefore we can just pass null to init() according to description in http://mxr.mozilla.org/comm-central/source/mozilla/widget/nsITransferable.idl#90
Updated•12 years ago
|
Attachment #664628 -
Flags: review?(philipp) → review+
Assignee | ||
Comment 2•12 years ago
|
||
Pushed to https://hg.mozilla.org/comm-central/rev/6482051d15a7
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
OS: Windows 7 → All
Hardware: x86_64 → All
Resolution: --- → FIXED
Target Milestone: --- → 2.0
Assignee | ||
Comment 3•12 years ago
|
||
Comment on attachment 664628 [details] [diff] [review] fix assertion failure and crash When trying to verify another bug in debug build I ran into this crash very often when using drag and drop or copying an event to clipboard. The patch and its risk for regressions are very small therefore I'd like to port this back to 1.9 beta.
Attachment #664628 -
Flags: approval-calendar-beta?
Updated•12 years ago
|
Attachment #664628 -
Flags: approval-calendar-beta? → approval-calendar-beta+
Assignee | ||
Comment 4•12 years ago
|
||
Ported back to https://hg.mozilla.org/releases/comm-beta/rev/2fe681068001
Target Milestone: 2.0 → 1.9
You need to log in
before you can comment on or make changes to this bug.
Description
•