[Webkit-unassigned] [Bug 42534] Crash in Notification::disconnectFrame() triggered by Frame::lifeSupportTimerFired()
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed Jul 21 09:26:01 PDT 2010
https://bugs.webkit.org/show_bug.cgi?id=42534
Yael <yael.aharon at nokia.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #62188|0 |1
is obsolete| |
Attachment #62188|review? |
Flag| |
Attachment #62193| |review?
Flag| |
--- Comment #11 from Yael <yael.aharon at nokia.com> 2010-07-21 09:26:01 PST ---
Created an attachment (id=62193)
--> (https://bugs.webkit.org/attachment.cgi?id=62193)
Patch
Added comment about the NULL check, per comment #10.
I am reluctant to add an ASSERT here, because if m_notificationPresenter will be NULL, Chromium will continue to crash and we will continue to get crash reports.
I assume these crash reports are generated from debug builds, not release builds, so the ASSERT will be hit.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list