Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-105082

QtWebEngine freezes on specific Chromium debug command

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: P2: Important P2: Important
    • 6.4.0 RC1, 6.5.0 Beta1
    • 6.2.5, 6.3.1
    • WebEngine
    • None
    • Windows 10
    • Windows
    • f2f6e3a3b2 (qt/qtwebengine/dev) f2f6e3a3b2 (qt/tqtc-qtwebengine/dev) 36ecbccef8 (qt/qtwebengine/6.3) cf34c27798 (qt/qtwebengine/6.4) 36ecbccef8 (qt/tqtc-qtwebengine/6.3) cf34c27798 (qt/tqtc-qtwebengine/6.4) 36ecbccef8 (qt/qtwebengine/6.3.2)

      I created a QtWebEngine instance and set Chromium into debug mode with setting the environment variable QTWEBENGINE_REMOTE_DEBUGGING.

      With the debug mode running, I connect to the debug websocket created by Chromium to dispatch debug commands via the ChromeDevTools protocol (see here). With one exception, all comands work. However, when I try to send the command Input.dispatchKeyEvent, the web engine freezes indefinitely. The commands are sent as seen here. The params used with the command have absolutely no effect on the outcome, as long as the command itself is valid.

      The thing is, when I try to do the same in the stock Chromium browser, using the same versions as Qt (tested with the Chromium versions of Qt 6.3.1 and 6.2.5), I have zero problems. The problems only shows in combination with the QtWebEngine, that's why I'm filing the bug here.

      So maybe there is a bug with how Qt uses Chromium?

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            qt_webengine_team Qt WebEngine Team
            avk111 Amarin Kloeker
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:

                There are no open Gerrit changes