Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. QtWebEngine
  4. Crash when using qml webengineview
QtWS25 Last Chance

Crash when using qml webengineview

Scheduled Pinned Locked Moved Solved QtWebEngine
qmlwebengineviewqt 5.12.0msvc2017crash
2 Posts 1 Posters 1.4k Views
  • 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.
  • C Offline
    C Offline
    convexbytes
    wrote on 15 Jan 2019, 01:32 last edited by
    #1

    Re: Can't use WebEngineView.

    Hi,
    I am getting random crashes when I use webengineview in debug mode

    [10980:14076:0114/163619.937:FATAL:com_init_util.cc(71)] Check failed: false. CoCreateInstance calls in Chromium require explicit COM initialization via base::CreateCOMSTATaskRunnerWithTraits() or ScopedCOMInitializer. See the comment in DCheckedCoCreateInstance for more details.
    

    My environment: windows10, msvc2017 32 bit, qt 5.12.0
    I also use axcontainer module to load an ActiveX object, this is a must for my application. I use these libraries
    QT += qml quick quickcontrols2
    QT += widgets
    QT += multimedia
    QT += core
    QT += webengine
    QT += axcontainer

    Is there any caveat when using together with other COM components?

    Please let me know if this is known error or give me any clue. I can post most information if required.

    1 Reply Last reply
    0
    • C Offline
      C Offline
      convexbytes
      wrote on 1 Jul 2019, 22:40 last edited by
      #2

      I wrote to chromium developers, so, here is the summary

      • It is not a crash, it is a failed debug assertion
      • It happens if:
        • you use webview's chromium backend (recent versions, old versions don't have this assertion)
        • some part of you code consumes COM and
        • that code's thread is not explicitly initializing COM via CoInitialize or CoInitializeEx

      My code uses a library that was not properly initializing COM in its threads before calling CoCreateInstance. Calling CoInitialize should fix my issue, but I cannot prove it until I have access to that libraries source code.

      What is left to be done by qt/webview team is to fix the failed assertion on "Chrome_InProcGpuThread" which is not created by user.

      1 Reply Last reply
      0

      • Login

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