Summary: | NULL pointer crash in dispatchEvent(null); | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Dean McNamee <deanm> | ||||
Component: | WebCore Misc. | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | ap, mihnea, sam, skylined | ||||
Priority: | P1 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Attachments: |
|
Description
Dean McNamee
2008-09-24 10:01:21 PDT
We seem to have the same issue in other dispatchEvent() implementations (why are there so many?). E.g. XMLHttpRequestUpload::dispatchEvent, DOMApplicationCache::dispatchEvent, MessagePort::dispatchEvent. (In reply to comment #1) > We seem to have the same issue in other dispatchEvent() implementations (why > are there so many?). E.g. XMLHttpRequestUpload::dispatchEvent, > DOMApplicationCache::dispatchEvent, MessagePort::dispatchEvent. Anders and I just discussed this yesterday. The functions seem generic enough that we should be able to factor them up to EventTarget (or elsewhere). Any word on this? Could we check in the simple NULL checks for now until it gets refactored? Yes. Would you be willing to make a patch with test cases? Created attachment 25601 [details]
patch
Comment on attachment 25601 [details]
patch
r=me
|