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. Debug error
Forum Updated to NodeBB v4.3 + New Features

Debug error

Scheduled Pinned Locked Moved Unsolved QtWebEngine
12 Posts 2 Posters 1.2k 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.
  • kkoehneK Offline
    kkoehneK Offline
    kkoehne
    Moderators
    wrote on last edited by
    #2

    Do you have Qt WebEngine module installed? That is, does D:\SimYog\thirdparty3-repo\Qt\5.9.9\msvc2017_64\bin or D:\SimYog\thirdparty3-repo\Qt\5.9.9\msvc2017_64\libexec contain a QtWebEngineProcessd.exe?

    Director R&D, The Qt Company

    Q 1 Reply Last reply
    0
    • kkoehneK kkoehne

      Do you have Qt WebEngine module installed? That is, does D:\SimYog\thirdparty3-repo\Qt\5.9.9\msvc2017_64\bin or D:\SimYog\thirdparty3-repo\Qt\5.9.9\msvc2017_64\libexec contain a QtWebEngineProcessd.exe?

      Q Offline
      Q Offline
      QtsCOde
      wrote on last edited by
      #3

      @kkoehne Yes its installed and is there in Qt 5.9.9 version.
      efa8a69c-1a63-4e8a-8898-2bc052df47e6-image.png

      Q 1 Reply Last reply
      0
      • Q QtsCOde

        @kkoehne Yes its installed and is there in Qt 5.9.9 version.
        efa8a69c-1a63-4e8a-8898-2bc052df47e6-image.png

        Q Offline
        Q Offline
        QtsCOde
        wrote on last edited by
        #4

        @QtsCOde What I am actually doing, I was running the application earlier in 6.5.0, but now i need to run it in 5.9.9, and I am getting this error, though QtWebEngineProcessd.exe is there is qt 5.9.9.

        kkoehneK 1 Reply Last reply
        0
        • Q QtsCOde

          @QtsCOde What I am actually doing, I was running the application earlier in 6.5.0, but now i need to run it in 5.9.9, and I am getting this error, though QtWebEngineProcessd.exe is there is qt 5.9.9.

          kkoehneK Offline
          kkoehneK Offline
          kkoehne
          Moderators
          wrote on last edited by kkoehne
          #5

          @QtsCOde Qt 5.9.9 is not exactly an up-to-date version of Qt. But I guess you have your reasons ...

          Looking at the code in question, it does look for following directories to locate QtWebEngineProcessd.exe:

          • %QTWEBENGINEPROCESS_PATH% environment variable
          • QLibraryInfo::location(QLibraryInfo::LibraryExecutablesPath) + "/QtWebEngineProcessd.exe"
          • QCoreApplication::applicationDirPath() + "/QtWebEngineProcessd.exe"

          QLibraryInfo::LibraryExecutablesPath in Qt 5.9.9 should be actually be D:\SimYog\thirdparty3-repo\Qt\5.9.9\msvc2017_64\bin , but maybe you have a qt.conf somewhere that changes that?

          Does it work if you set QTWEBENGINEPROCESS_PATH in your environment to D:\SimYog\thirdparty3-repo\Qt\5.9.9\msvc2017_64\bin\QtWebEngineProcessd.exe ?

          Director R&D, The Qt Company

          Q 1 Reply Last reply
          0
          • kkoehneK kkoehne

            @QtsCOde Qt 5.9.9 is not exactly an up-to-date version of Qt. But I guess you have your reasons ...

            Looking at the code in question, it does look for following directories to locate QtWebEngineProcessd.exe:

            • %QTWEBENGINEPROCESS_PATH% environment variable
            • QLibraryInfo::location(QLibraryInfo::LibraryExecutablesPath) + "/QtWebEngineProcessd.exe"
            • QCoreApplication::applicationDirPath() + "/QtWebEngineProcessd.exe"

            QLibraryInfo::LibraryExecutablesPath in Qt 5.9.9 should be actually be D:\SimYog\thirdparty3-repo\Qt\5.9.9\msvc2017_64\bin , but maybe you have a qt.conf somewhere that changes that?

            Does it work if you set QTWEBENGINEPROCESS_PATH in your environment to D:\SimYog\thirdparty3-repo\Qt\5.9.9\msvc2017_64\bin\QtWebEngineProcessd.exe ?

            Q Offline
            Q Offline
            QtsCOde
            wrote on last edited by QtsCOde
            #6

            @kkoehne Okay so I tried adding the path, and now the following error comes on running in release mode of v5.9.9
            162519f2-6668-48e5-9023-36c8b7ce9ff2-image.png
            And while running in debug mode this error comes
            bf7fea6a-1463-408f-ba63-d7007d76f1b3-image.png

            kkoehneK 1 Reply Last reply
            0
            • Q QtsCOde

              @kkoehne Okay so I tried adding the path, and now the following error comes on running in release mode of v5.9.9
              162519f2-6668-48e5-9023-36c8b7ce9ff2-image.png
              And while running in debug mode this error comes
              bf7fea6a-1463-408f-ba63-d7007d76f1b3-image.png

              kkoehneK Offline
              kkoehneK Offline
              kkoehne
              Moderators
              wrote on last edited by
              #7

              So somehow, the application causes a debug breakpoint (interrupt 3).

              Try to validate the assumptions in the surrounding code. Is m_webView->page() actually a valid pointer? Can you get a stack trace? Maybe try running your application with '--single-process'?

              https://doc.qt.io/qt-5/qtwebengine-debugging.html documents some Qt WebEngine features that might help you in debugging ...

              Director R&D, The Qt Company

              Q 1 Reply Last reply
              0
              • kkoehneK kkoehne

                So somehow, the application causes a debug breakpoint (interrupt 3).

                Try to validate the assumptions in the surrounding code. Is m_webView->page() actually a valid pointer? Can you get a stack trace? Maybe try running your application with '--single-process'?

                https://doc.qt.io/qt-5/qtwebengine-debugging.html documents some Qt WebEngine features that might help you in debugging ...

                Q Offline
                Q Offline
                QtsCOde
                wrote on last edited by
                #8

                @kkoehne Yes it is a vaid pointer because when I am trying to run in v.6.5 its running smoothly, but in v5.9.9 its giving this problem

                kkoehneK 1 Reply Last reply
                0
                • Q QtsCOde

                  @kkoehne Yes it is a vaid pointer because when I am trying to run in v.6.5 its running smoothly, but in v5.9.9 its giving this problem

                  kkoehneK Offline
                  kkoehneK Offline
                  kkoehne
                  Moderators
                  wrote on last edited by kkoehne
                  #9

                  @QtsCOde well, that it's a valid pointer in 6.5 doesn't necessarily mean that it's a valid pointer in Qt 5.9 , as there is quite obviously a difference , somewhere :) Anyhow, this is all just speculation. I guess you need to experiment a bit, and try to get a decent stack trace.

                  Director R&D, The Qt Company

                  Q 1 Reply Last reply
                  0
                  • kkoehneK kkoehne

                    @QtsCOde well, that it's a valid pointer in 6.5 doesn't necessarily mean that it's a valid pointer in Qt 5.9 , as there is quite obviously a difference , somewhere :) Anyhow, this is all just speculation. I guess you need to experiment a bit, and try to get a decent stack trace.

                    Q Offline
                    Q Offline
                    QtsCOde
                    wrote on last edited by
                    #10

                    @kkoehne okay, I will try to implement it. Btw, thank you so much.

                    Q 1 Reply Last reply
                    0
                    • Q QtsCOde

                      @kkoehne okay, I will try to implement it. Btw, thank you so much.

                      Q Offline
                      Q Offline
                      QtsCOde
                      wrote on last edited by
                      #11
                      This post is deleted!
                      1 Reply Last reply
                      0
                      • kkoehneK Offline
                        kkoehneK Offline
                        kkoehne
                        Moderators
                        wrote on last edited by
                        #12

                        This unfortunately doesn't tell much more than 'it crashed', either.

                        It's been a while that I've been working with WebEngine, and I'm also not sure which IDE you're using (is that VS Code)? Anyhow, the first thing you need is a proper stack trace, that tells you exactly which calls lead to the crash. This should be visible somewhere in your IDE after the crash when launching your app in debug mode.

                        You can also try the tips at https://wiki.qt.io/QtWebEngine/ReportingCrashes .

                        Director R&D, The Qt Company

                        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