RESOLVED INVALID 12946
crashes when visiting above URL 
https://bugs.webkit.org/show_bug.cgi?id=12946
Summary crashes when visiting above URL
Feng Qian
Reported 2007-03-02 10:16:28 PST
First 10 stack traces showed in GDB: #0 0x014695e5 in WTF::RefPtr<WebCore::StringImpl>::operator! (this=0x0) at RefPtr.h:52 #1 0x01190743 in WebCore::String::length (this=0x0) at /Users/fqian/WebKit/WebCore/platform/String.cpp:177 #2 0x010bf383 in WebCore::Document::parseQualifiedName (qualifiedName=@0x0, prefix=@0xbfffe4b0, localName=@0xbfffe4ac) at /Users/fqian/WebKit/WebCore/dom/Document.cpp:2504 #3 0x010c187d in WebCore::Document::createElementNS (this=0xbfffe7a8, _namespaceURI=@0x0, qualifiedName=@0x0, ec=@0x0) at /Users/fqian/WebKit/WebCore/dom/Document.cpp:674 #4 0x01249045 in KJS::Window::getOwnPropertySlot (this=0x16f6e4f0, exec=0xbfffe7a8, propertyName=@0x16f900ec, slot=@0xbfffe614) at /Users/fqian/WebKit/WebCore/bindings/js/kjs_window.cpp:984 #5 0x0152de8f in KJS::getStaticValueSlot<WebCore::JSDOMWindow, KJS::Window> (exec=0xbfffe7a8, table=0x15f9970, thisObj=0x16f6e4f0, propertyName=@0x16f900ec, slot=@0xbfffe614) at lookup.h:220 #6 0x0124bcef in WebCore::JSDOMWindow::getOwnPropertySlot (this=0x16f6e4f0, exec=0xbfffe7a8, propertyName=@0x16f900ec, slot=@0xbfffe614) at /Users/fqian/WebKit/WebKitBuild/Debug/DerivedSources/WebCore/JSDOMWindow.cpp:256 #7 0x0055f81b in KJS::JSObject::getPropertySlot (this=0x16f6e4f0, exec=0xbfffe7a8, propertyName=@0x16f900ec, slot=@0xbfffe614) at object.h:555 #8 0x004fa54e in KJS::JSObject::hasProperty (this=0x16f6e4f0, exec=0xbfffe7a8, propertyName=@0x16f900ec) at /Users/fqian/WebKit/JavaScriptCore/kjs/object.cpp:304 #9 0x004ea551 in KJS::VarDeclNode::processVarDecls (this=0x16f900e0, exec=0xbfffe7a8) at /Users/fqian/WebKit/JavaScriptCore/kjs/nodes.cpp:1584 #10 0x004ea5ff in KJS::VarDeclListNode::processVarDecls (this=0x16f90100, exec=0xbfffe7a8) at /Users/fqian/WebKit/JavaScriptCore/kjs/nodes.cpp:1609
Attachments
Add attachment proposed patch, testcase, etc.
Feng Qian
Comment 1 2007-03-02 10:47:10 PST
Sorry, that's probably because my local build messed up. After a clean build, the problem is not reproducible. Close it.
Note You need to log in before you can comment on or make changes to this bug.