Upgrade to Qt 6.6.0 breaks Qt.openUrlExternally

Michel de Boer

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?

SGaist

Hi,

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

On which platform are you getting that ?

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.

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

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?

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.

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.

Michel de Boer

@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.