[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:54:24 PDT 2010
https://bugs.webkit.org/show_bug.cgi?id=42534
--- Comment #16 from John Gregg <johnnyg at google.com> 2010-07-21 09:54:23 PST ---
(In reply to comment #14)
> (In reply to comment #13)
> > > I assume these crash reports are generated from debug builds, not release builds, so the ASSERT will be hit.
> >
> > This sounds surprising - I never heard that any vendor shipped a debug build of WebKit to users.
>
> I don't know where these crash logs come from. Maybe someone from Chromium project could tell us.
> However, if you look at all other functions of NotificationCenter, there is a NULL check in each one of them, so I don't understand why it is a problem to have a NULL check in this new function as well?
The crash reports are from release builds, not debug builds, so I think that the ASSERT would be fine.
--
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