Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. QML and Qt Quick
  4. Upgrade to Qt 6.6.0 breaks Qt.openUrlExternally
Forum Updated to NodeBB v4.3 + New Features

Upgrade to Qt 6.6.0 breaks Qt.openUrlExternally

Scheduled Pinned Locked Moved Solved QML and Qt Quick
8 Posts 3 Posters 860 Views 2 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.
  • M Offline
    M Offline
    Michel de Boer
    wrote on last edited by
    #1

    In my QML code I open URL in an external browser like this:

    Qt.openUrlExternally(link)
    

    When I compile with Qt 6.5.3 it works fine
    .
    When I compile with Qt 6.6.0 the external web browser opens the link, but my application terminates with exit code 1.

    Is this a bug in Qt 6.6.0?

    1 Reply Last reply
    0
    • SGaistS Offline
      SGaistS Offline
      SGaist
      Lifetime Qt Champion
      wrote on last edited by
      #2

      Hi,

      It does look at least unexpected. Do you have a stack trace of your application ?

      On which platform are you getting that ?

      Interested in AI ? www.idiap.ch
      Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

      M 1 Reply Last reply
      0
      • SGaistS SGaist

        Hi,

        It does look at least unexpected. Do you have a stack trace of your application ?

        On which platform are you getting that ?

        M Offline
        M Offline
        Michel de Boer
        wrote on last edited by
        #3

        @SGaist It happens on Linux.
        On Android it still works fine.

        I do not have a stack trace. The program just exits with an exit code of 1. I tried to run it in the debugger. When I do I get nothing useful; it looks like an empty stack.

        kkoehneK 1 Reply Last reply
        0
        • M Michel de Boer

          @SGaist It happens on Linux.
          On Android it still works fine.

          I do not have a stack trace. The program just exits with an exit code of 1. I tried to run it in the debugger. When I do I get nothing useful; it looks like an empty stack.

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

          @Michel-de-Boer is this reproducible with one of the Qt examples? E.g. the 'File System Explorer" example uses this API when you click on the 'world' icon on the bottom left...

          If you have something reproducible in a smaller application, please file a bug at https://bugreports.qt.io

          Director R&D, The Qt Company

          M 1 Reply Last reply
          0
          • kkoehneK kkoehne

            @Michel-de-Boer is this reproducible with one of the Qt examples? E.g. the 'File System Explorer" example uses this API when you click on the 'world' icon on the bottom left...

            If you have something reproducible in a smaller application, please file a bug at https://bugreports.qt.io

            M Offline
            M Offline
            Michel de Boer
            wrote on last edited by
            #5

            @kkoehne I can reproduce it with the "File System Exporer" when I add this to CMakeLists.txt

            add_compile_options(-fsanitize=address)
            add_link_options(-fsanitize=address)
            

            I have that in my project to enable the address sanitizer.
            Without the address sanitizer it all works fine.

            NOTE: in Qt 6.5.3 it works fine with the address sanitizer enabled.

            Should I file a bug for this?

            kkoehneK 1 Reply Last reply
            0
            • M Michel de Boer

              @kkoehne I can reproduce it with the "File System Exporer" when I add this to CMakeLists.txt

              add_compile_options(-fsanitize=address)
              add_link_options(-fsanitize=address)
              

              I have that in my project to enable the address sanitizer.
              Without the address sanitizer it all works fine.

              NOTE: in Qt 6.5.3 it works fine with the address sanitizer enabled.

              Should I file a bug for this?

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

              @Michel-de-Boer interesting ... this sounds like address-sanitizer somehow clashes with QProcess?

              Yes, please file a bug , including the exact gcc version you're using. As this is limited to address-sanitizer, it might also be a compiler problem ... I can't promise anyone will look into it right away though.

              Director R&D, The Qt Company

              kkoehneK 1 Reply Last reply
              0
              • kkoehneK kkoehne

                @Michel-de-Boer interesting ... this sounds like address-sanitizer somehow clashes with QProcess?

                Yes, please file a bug , including the exact gcc version you're using. As this is limited to address-sanitizer, it might also be a compiler problem ... I can't promise anyone will look into it right away though.

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

                From the changes in https://code.qt.io/cgit/qt/qtbase.git/log/src/corelib/io/qprocess_unix.cpp?h=6.6.0, there's at least some wresting with asan for QProcess, so this might be related.

                Director R&D, The Qt Company

                M 1 Reply Last reply
                0
                • kkoehneK kkoehne

                  From the changes in https://code.qt.io/cgit/qt/qtbase.git/log/src/corelib/io/qprocess_unix.cpp?h=6.6.0, there's at least some wresting with asan for QProcess, so this might be related.

                  M Offline
                  M Offline
                  Michel de Boer
                  wrote on last edited by
                  #8

                  @kkoehne sounds like it!

                  I have created: https://bugreports.qt.io/browse/QTBUG-119210

                  I am not in a hurry to get this fixed. Now that I know that is ASAN, I can easily work around it. I only use ASAN in my debug build.

                  1 Reply Last reply
                  0
                  • M Michel de Boer has marked this topic as solved on

                  • Login

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