The crash happens when Web Inspector is on and javascript is paused. In this case, the debugger calls WebCore::ScriptDebugServer::pauseIfNeeded(), and inside it enters another level of event loop. The problem is that once the loop is exited, the state of data, especially *page->group()->pages().begin(), is unstable, and this page is probably during destruction process or it may even be a dangling pointer. This way, when setJavaScriptPaused with this page results in crash. I suspect the system doesn't predict that the event loop may happen to be exited in this function instead of the main event loop in the application that uses webkit. This behavior can be reproduced with WebKit-efl, as well as with Arora [Webkit-Qt] (although I haven't observed it with Rekonq [Webkit-KDE]): 1. Run Arora with any page (preferably under gdb because without it the crash may be unable to be observed) 2. Open Web Inspector 3. Click "Scripts" and pause javascript (make sure that you can see the backtrace) 4. Close the Arora window I know you can think that it's insignificant that a crash happens when you close the program. The problem is, though, that this problem occurs also when you close a widget realized by WRT engine, and in this case the whole WRT engine crashes, not only the widget being closed.
*** This bug has been marked as a duplicate of bug 44230 ***
I don't think this is a dupe of bug 44230, that bug is about Mac and about closign the window. This is abotu EFL and Qt in Arora.
Reopening.
Is this still an issue? Migrating to new component.
<rdar://problem/15909919>
Closing this bug because the EFL port has been removed from trunk. If you feel this bug applies to a different upstream WebKit port and was closed in error, please either update the title and reopen the bug, or leave a comment to request this.