Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. QtWebEngine
  4. QtWebEngine 6.8.5 crashes (SIGSEGV) on YouTube video playback — IndexedDB reopen bug in IndexedDBBucketContext::OpenDatabase
Qt 6.12 LTS is out! See what's new in the release blog

QtWebEngine 6.8.5 crashes (SIGSEGV) on YouTube video playback — IndexedDB reopen bug in IndexedDBBucketContext::OpenDatabase

Scheduled Pinned Locked Moved Solved QtWebEngine
qtwebenginecross-compileraspberry pi 5qt6
3 Posts 2 Posters 72 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • T Offline
    T Offline
    The Qt Mayssa
    wrote last edited by
    #1

    1. Compiler
    Reproduced identically across GCC 13, GCC 14, and Clang 14 — confirmed independent of compiler/toolchain.
    Build toolchain used for the affected build: crossbuild-essential-arm64 (GCC 13) on Ubuntu 24.04, cross-compiling to aarch64.

    2. Operating system
    Target (affected): Raspberry Pi 5, Debian 13 “trixie” (aarch64).
    Build host: Ubuntu 24.04 (x86_64), cross-compilation via sysroot.
    Reference (not affected): Debian 13 “trixie” desktop (x86_64), QtWebEngine 6.8.2 installed natively via apt — no cross-compilation involved.

    3. Qt version and configure options

    • Qt (affected build): 6.8.5
    • QtWebEngine (embedded Chromium): 122.0.6261.171 (extracted from the compiled libQt6WebEngineCore.so.6.8.5)
    • qtbase configure:
    configure -prefix <prefix> -extprefix <extprefix> -qt-host-path <hostQt> -release \
      -opengl es2 -egl -qpa wayland -no-feature-xcb -openssl-linked \
      -nomake examples -nomake tests -- -DCMAKE_TOOLCHAIN_FILE=<toolchain.cmake>
    
    • qtwebengine module configure: -DFEATURE_webengine_proprietary_codecs=ON

    4. Steps to reproduce (100% reproducible with a fresh profile)

    • Launch a QtWebEngine view (fresh/empty profile, no prior cache).
    • Navigate to any YouTube video page.
    • Within a few seconds, the process crashes with SIGSEGV.
    • Confirmed with a minimal IndexedDB open → write → close → reopen → read test page (not just YouTube) — the crash occurs specifically when re-opening an IndexedDB connection that was already open.

    Why the reference build does not crash
    QtWebEngine 6.8.2, installed via apt on a Debian 13 “trixie” desktop (x86_64, native build, no cross-compilation), does not crash on the same scenario. Same Chromium base (122) as our 6.8.5, but a different Chromium security patch level (132 vs 141) — the bug was most likely introduced by a security fix backported between those two levels, present in 6.8.5 but not in 6.8.2.

    Questions for the Qt team

    • Is this already a known/reported issue on this tracker (we searched but may have missed it — the symptom “QtWebEngine crashes reopening IndexedDB” may be filed under a more generic title)?
    • Would building against a different 6.8.x patch release (or against 6.9/6.10/6.11, where QtWebEngine source is already published) sidestep this, or does it carry the same backported security fix?
    • What’s the recommended workaround/timeline, given QtWebEngine source for Qt 6.12.0 (the current LTS) is not published yet on download.qt.io — we can’t simply move to the newest LTS to get a fixed WebEngine today?
    JKSHJ 1 Reply Last reply
    0
    • T The Qt Mayssa

      1. Compiler
      Reproduced identically across GCC 13, GCC 14, and Clang 14 — confirmed independent of compiler/toolchain.
      Build toolchain used for the affected build: crossbuild-essential-arm64 (GCC 13) on Ubuntu 24.04, cross-compiling to aarch64.

      2. Operating system
      Target (affected): Raspberry Pi 5, Debian 13 “trixie” (aarch64).
      Build host: Ubuntu 24.04 (x86_64), cross-compilation via sysroot.
      Reference (not affected): Debian 13 “trixie” desktop (x86_64), QtWebEngine 6.8.2 installed natively via apt — no cross-compilation involved.

      3. Qt version and configure options

      • Qt (affected build): 6.8.5
      • QtWebEngine (embedded Chromium): 122.0.6261.171 (extracted from the compiled libQt6WebEngineCore.so.6.8.5)
      • qtbase configure:
      configure -prefix <prefix> -extprefix <extprefix> -qt-host-path <hostQt> -release \
        -opengl es2 -egl -qpa wayland -no-feature-xcb -openssl-linked \
        -nomake examples -nomake tests -- -DCMAKE_TOOLCHAIN_FILE=<toolchain.cmake>
      
      • qtwebengine module configure: -DFEATURE_webengine_proprietary_codecs=ON

      4. Steps to reproduce (100% reproducible with a fresh profile)

      • Launch a QtWebEngine view (fresh/empty profile, no prior cache).
      • Navigate to any YouTube video page.
      • Within a few seconds, the process crashes with SIGSEGV.
      • Confirmed with a minimal IndexedDB open → write → close → reopen → read test page (not just YouTube) — the crash occurs specifically when re-opening an IndexedDB connection that was already open.

      Why the reference build does not crash
      QtWebEngine 6.8.2, installed via apt on a Debian 13 “trixie” desktop (x86_64, native build, no cross-compilation), does not crash on the same scenario. Same Chromium base (122) as our 6.8.5, but a different Chromium security patch level (132 vs 141) — the bug was most likely introduced by a security fix backported between those two levels, present in 6.8.5 but not in 6.8.2.

      Questions for the Qt team

      • Is this already a known/reported issue on this tracker (we searched but may have missed it — the symptom “QtWebEngine crashes reopening IndexedDB” may be filed under a more generic title)?
      • Would building against a different 6.8.x patch release (or against 6.9/6.10/6.11, where QtWebEngine source is already published) sidestep this, or does it carry the same backported security fix?
      • What’s the recommended workaround/timeline, given QtWebEngine source for Qt 6.12.0 (the current LTS) is not published yet on download.qt.io — we can’t simply move to the newest LTS to get a fixed WebEngine today?
      JKSHJ Offline
      JKSHJ Offline
      JKSH
      Moderators
      wrote last edited by
      #2

      @The-Qt-Mayssa said in QtWebEngine 6.8.5 crashes (SIGSEGV) on YouTube video playback — IndexedDB reopen bug in IndexedDBBucketContext::OpenDatabase:

      QtWebEngine source for Qt 6.12.0 (the current LTS) is not published yet on download.qt.io — we can’t simply move to the newest LTS to get a fixed WebEngine today?

      Qt WebEngine has been split out of Qt, with a separate release cycle and separate package:

      • https://www.qt.io/blog/qt-webengine-will-release-separate
      • https://download.qt.io/official_releases/qtwebengine/6.140/6.140.0/src/

      See also the release note at https://code.qt.io/cgit/qt/qtreleasenotes.git/about/qtwebengine/6.140.0/release-note.md

      Questions for the Qt team

      • Is this already a known/reported issue on this tracker (we searched but may have missed it — the symptom “QtWebEngine crashes reopening IndexedDB” may be filed under a more generic title)?
      • Would building against a different 6.8.x patch release (or against 6.9/6.10/6.11, where QtWebEngine source is already published) sidestep this, or does it carry the same backported security fix?

      I don't know, and I'm not part of the Qt team. Can you please test the latest release and let us know the outcome?

      Qt Doc Search for browsers: forum.qt.io/topic/35616/web-browser-extension-for-improved-doc-searches

      T 1 Reply Last reply
      2
      • JKSHJ JKSH

        @The-Qt-Mayssa said in QtWebEngine 6.8.5 crashes (SIGSEGV) on YouTube video playback — IndexedDB reopen bug in IndexedDBBucketContext::OpenDatabase:

        QtWebEngine source for Qt 6.12.0 (the current LTS) is not published yet on download.qt.io — we can’t simply move to the newest LTS to get a fixed WebEngine today?

        Qt WebEngine has been split out of Qt, with a separate release cycle and separate package:

        • https://www.qt.io/blog/qt-webengine-will-release-separate
        • https://download.qt.io/official_releases/qtwebengine/6.140/6.140.0/src/

        See also the release note at https://code.qt.io/cgit/qt/qtreleasenotes.git/about/qtwebengine/6.140.0/release-note.md

        Questions for the Qt team

        • Is this already a known/reported issue on this tracker (we searched but may have missed it — the symptom “QtWebEngine crashes reopening IndexedDB” may be filed under a more generic title)?
        • Would building against a different 6.8.x patch release (or against 6.9/6.10/6.11, where QtWebEngine source is already published) sidestep this, or does it carry the same backported security fix?

        I don't know, and I'm not part of the Qt team. Can you please test the latest release and let us know the outcome?

        T Offline
        T Offline
        The Qt Mayssa
        wrote last edited by
        #3

        @JKSH
        Update: tested & approved ;) thank you !
        No more crashs with the latest release

        1 Reply Last reply
        0
        • T The Qt Mayssa has marked this topic as solved

        • Login

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups
        • Search
        • Get Qt
        • Unsolved