RESOLVED DUPLICATE of bug 13942 Bug 14620
ASSERTION FAILED: !attrName.contains('/') in WebCore::Token::addAttribute
https://bugs.webkit.org/show_bug.cgi?id=14620
Summary ASSERTION FAILED: !attrName.contains('/') in WebCore::Token::addAttribute
David Kilzer (:ddkilzer)
Reported 2007-07-14 12:05:01 PDT
* SUMMARY Opening a webarchive then inspecting it causes an assertion failure. * STEPS TO REPRODUCE 1. Launch Safari/WebKit. 2. Open a webarchive. (I used Attachment 14729 [details] on Bug 13813.) 3. Right click on the huge "At a Glance" tab and select "Inspect Element". * EXPECTED RESULTS The Web Inspector should come up. * ACTUAL RESULTS Safari crashes. * REGRESSION Only tested with a local debug build of WebKit r24285 with Safari 3.0 (522.12) on Mac OS X 10.4.10 (8R218). * NOTES Console output: ASSERTION FAILED: !attrName.contains('/') (/path/to/WebKit/WebCore/html/HTMLTokenizer.cpp:132 void WebCore::Token::addAttribute(WebCore::Document*, WebCore::AtomicString&, const WebCore::AtomicString&, bool)) Segmentation fault Stack trace will be attached.
Attachments
Crash log (31.15 KB, text/plain)
2007-07-14 12:07 PDT, David Kilzer (:ddkilzer)
no flags
David Kilzer (:ddkilzer)
Comment 1 2007-07-14 12:07:22 PDT
Created attachment 15518 [details] Crash log
Adele Peterson
Comment 2 2007-08-30 15:50:46 PDT
doesn't seem to have an effect in release builds.
Matt Lilek
Comment 3 2007-09-01 11:41:02 PDT
I'm hitting this on Windows XP with r25334 just by visiting <http://www.allaboutolive.com.au/>.
David Kilzer (:ddkilzer)
Comment 4 2007-10-09 07:00:29 PDT
Probably a duplicate of Bug 14620. Need to compare the source for the webarchive to the live web pages.
David Kilzer (:ddkilzer)
Comment 5 2007-10-09 07:04:23 PDT
(In reply to comment #4) > Probably a duplicate of Bug 14620. Need to compare the source for the > webarchive to the live web pages. Err...a duplicate of Bug 13942. It's way too early.
David Kilzer (:ddkilzer)
Comment 6 2008-03-06 10:51:04 PST
*** This bug has been marked as a duplicate of 13942 ***
Note You need to log in before you can comment on or make changes to this bug.