Bug 29748 - Null-deref when first access to an Attr node is after its Element is destroyed
Summary: Null-deref when first access to an Attr node is after its Element is destroyed
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Darin Adler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-25 13:38 PDT by Darin Adler
Modified: 2019-02-06 09:04 PST (History)
1 user (show)

See Also:


Attachments
patch (15.49 KB, patch)
2009-09-25 13:49 PDT, Darin Adler
ggaren: review+
Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Darin Adler 2009-09-25 13:38:42 PDT
We noticed that if your first access to an Attr node is after its Element is destroyed, you crash due to a null-dereference. This needs to be fixed.
Comment 1 Darin Adler 2009-09-25 13:49:58 PDT
Created attachment 40141 [details]
patch
Comment 2 Geoffrey Garen 2009-09-25 14:03:57 PDT
Comment on attachment 40141 [details]
patch

r=me
Comment 3 Darin Adler 2009-09-28 12:40:44 PDT
http://trac.webkit.org/changeset/48769
Comment 4 Lucas Forschler 2019-02-06 09:04:00 PST
Mass moving XML DOM bugs to the "DOM" Component.