[Webkit-unassigned] [Bug 71271] [Qt] Web Inspector: inspector UI becomes unresponsive on debugger pause

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sun Jan 15 11:28:19 PST 2012


https://bugs.webkit.org/show_bug.cgi?id=71271


Mozhaev Grigory <zcrendel at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |zcrendel at gmail.com




--- Comment #1 from Mozhaev Grigory <zcrendel at gmail.com>  2012-01-15 11:28:19 PST ---
The bug still exists. I tested it on Windows and Linux platforms. It works fine with webkit from Qt-4.7.4 but doesn't work with webkit from trunk and from Qt-4.8.

I did some rough hack - removed isPaused() statement from a couple of the conditions in the following source files:

   WebCore/bindings/js/JSLazyEventListener.cpp (in ScriptValue ScriptController::executeScriptInWorld() func)
   WebCore/bindings/js/ScriptController.cpp (in JSLazyEventListener::initializeJSFunction() func)
   WebCore/bindings/js/JSEventListener.cpp (in JSEventListener::handleEvent() func)

Just like that:
   if (!script->canExecuteScripts(AboutToExecuteScript))// || script->isPaused())

and then GUI becomes partially responsive. After this I did a little bit more research and have got that:
when breakpoint paused - nothing changed in GUI, although "Debugger.paused" message sent to frontend page with success, but didn't executed (due to locked JS context). If you clicked on 'workers debug' combobox (or any other GUI part which interacts with backend) and then this method will be executed and GUI will be updated to paused state.

Hope it can help somehow.

I think that solving of this bug is very important (not just P2) - because no way to make local debug of javascript from inspector while it still there and it's very annoying for js developers who use qt-webkit.

Any clues?

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list