Bug 52533
| Summary: | Web Inspector: [REGRESSION][CRASH] Closing inspected tab on latest nightly crashes Safari. | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Pavel Feldman <pfeldman> |
| Component: | Web Inspector (Deprecated) | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | apavlov, bweinstein, joepeck, keishi, loislo, pfeldman, pmuellr, rik, timothy, yurys |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
Pavel Feldman
#0 0x7fff82b94120 in objc_msgSend
#1 0x100fb9431 in -[WebInspectorWindowController close] at WebInspectorClient.mm:327
#2 0x100fb82fc in -[WebInspectorWindowController destroyInspectorView:] at WebInspectorClient.mm:454
#3 0x100fb78df in WebInspectorFrontendClient::disconnectFromBackend at WebInspectorClient.mm:177
#4 0x101ad4835 in WebCore::InspectorFrontendHost::disconnectFromBackend at InspectorFrontendHost.cpp:172
#5 0x101c374a1 in WebCore::jsInspectorFrontendHostPrototypeFunctionDisconnectFromBackend at JSInspectorFrontendHost.cpp:223
#6 0x246fbee001b8 in ??
#7 0x1007e363d in JSC::JITCode::execute at JITCode.h:77
#8 0x1007de42d in JSC::Interpreter::executeCall at Interpreter.cpp:849
#9 0x1007965fc in JSC::call at CallData.cpp:38
#10 0x101b157bf in WebCore::JSMainThreadExecState::call at JSMainThreadExecState.h:48
#11 0x101ffcea1 in WebCore::ScheduledAction::executeFunctionInContext at ScheduledAction.cpp:106
#12 0x101ffd3cc in WebCore::ScheduledAction::execute at ScheduledAction.cpp:128
#13 0x101ffd4a6 in WebCore::ScheduledAction::execute at ScheduledAction.cpp:76
#14 0x101812b4b in WebCore::DOMTimer::fired at DOMTimer.cpp:131
#15 0x1021955dc in WebCore::ThreadTimers::sharedTimerFiredInternal at ThreadTimers.cpp:112
#16 0x10219576b in WebCore::ThreadTimers::sharedTimerFired at ThreadTimers.cpp:90
#17 0x1020598b5 in WebCore::timerFired at SharedTimerMac.mm:166
EXC_BAD_ACCESS
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
*** This bug has been marked as a duplicate of bug 44230 ***