RESOLVED WORKSFORME 45758
Web Inspector: [JSC] browser crashes if breakpoint is hit when JS profiling is active 
https://bugs.webkit.org/show_bug.cgi?id=45758
Summary Web Inspector: [JSC] browser crashes if breakpoint is hit when JS profiling i...
Yury Semikhatsky
Reported 2010-09-14 09:22:10 PDT
[JSC] Web Inspector: browser crashes if breakpoint is hit when JS profiling is active Steps to reproduce: 1. Navigate browser to the attached document 2. Open inspector 3. Open scripts panel and make sure debugging is enabled 4. Go to Profiles panel and enable profiling 5. Go to the inspected page and press the button to trigger debug break Result: Browser crashes.
Attachments
The test document (120 bytes, text/html)
2010-09-14 09:22 PDT, Yury Semikhatsky 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Yury Semikhatsky
Comment 1 2010-09-14 09:22:45 PDT
Created attachment 67564 [details] The test document
Yury Semikhatsky
Comment 2 2010-09-14 09:30:11 PDT
#0 0x007b9e65 in JSC::JSGlobalObject::d at JSGlobalObject.h:278 #1 0x007ecd51 in JSC::JSGlobalObject::profileGroup at JSGlobalObject.h:251 #2 0x007effea in JSC::Profiler::didExecute at Profiler.cpp:130 #3 0x00714cf9 in JSC::Interpreter::executeCall at Interpreter.cpp:788 #4 0x006cfd1b in JSC::call at CallData.cpp:38 #5 0x048bb852 in WebCore::JSMainThreadExecState::call at JSMainThreadExecState.h:48 #6 0x04db4996 in WebCore::ScriptFunctionCall::call at ScriptFunctionCall.cpp:150 #7 0x04db4a64 in WebCore::ScriptFunctionCall::call at ScriptFunctionCall.cpp:165 #8 0x047f71dd in WebCore::InjectedScript::callFrames at InjectedScript.cpp:69 #9 0x04866430 in WebCore::InspectorDebuggerAgent::currentCallFrames at InspectorDebuggerAgent.cpp:217 #10 0x04866539 in WebCore::InspectorDebuggerAgent::didPause at InspectorDebuggerAgent.cpp:295 #11 0x04da4d27 in WebCore::ScriptDebugServer::dispatchDidPause at ScriptDebugServer.cpp:266 #12 0x04da46e0 in WebCore::ScriptDebugServer::dispatchFunctionToListeners at ScriptDebugServer.cpp:359 #13 0x04da47b8 in WebCore::ScriptDebugServer::dispatchFunctionToListeners at ScriptDebugServer.cpp:371 #14 0x04da510f in WebCore::ScriptDebugServer::pauseIfNeeded at ScriptDebugServer.cpp:452 #15 0x04da52ec in WebCore::ScriptDebugServer::didReachBreakpoint at ScriptDebugServer.cpp:569 #16 0x007134b8 in JSC::Interpreter::debug at Interpreter.cpp:1134 #17 0x00740b39 in cti_op_debug at JITStubs.cpp:3552 #18 0x0073f322 in WTF::doubleHash at HashTable.h:447 #19 0x0071930b in JSC::JITCode::execute at JITCode.h:77 #20 0x00714c5a in JSC::Interpreter::executeCall at Interpreter.cpp:780 #21 0x006cfd1b in JSC::call at CallData.cpp:38 #22 0x048bb852 in WebCore::JSMainThreadExecState::call at JSMainThreadExecState.h:48 #23 0x049683ad in WebCore::JSEventListener::handleEvent at JSEventListener.cpp:124 #24 0x046adcfa in WebCore::EventTarget::fireEventListeners at EventTarget.cpp:339 #25 0x046ae30c in WebCore::EventTarget::fireEventListeners at EventTarget.cpp:300 #26 0x04bc24db in WebCore::Node::handleLocalEvents at Node.cpp:2510 #27 0x04bc2c0d in WebCore::Node::dispatchGenericEvent at Node.cpp:2653 #28 0x04bc310f in WebCore::Node::dispatchEvent at Node.cpp:2573 #29 0x04bc1259 in WebCore::Node::dispatchMouseEvent at Node.cpp:2865 #30 0x04bc1761 in WebCore::Node::dispatchMouseEvent at Node.cpp:2774 #31 0x0469c081 in WebCore::EventHandler::dispatchMouseEvent at EventHandler.cpp:1841 #32 0x0469f674 in WebCore::EventHandler::handleMouseReleaseEvent at EventHandler.cpp:1569 #33 0x046a7f47 in WebCore::EventHandler::mouseUp at EventHandlerMac.mm:545 #34 0x00d583c1 in -[WebHTMLView mouseUp:] at WebHTMLView.mm:3728 #35 0x96155b95 in -[NSWindow sendEvent:] #36 0x0003ffaa in ?? #37 0x0003ff37 in ?? #38 0x961226a5 in -[NSApplication sendEvent:] #39 0x000371cc in ?? #40 0x9607ffe7 in -[NSApplication run] #41 0x9604d1d8 in NSApplicationMain
Note You need to log in before you can comment on or make changes to this bug.