Qt Creator 16.0.0 is crashing when opening cpp files

[jsulm]

@mithune0000 If you start QtCreator from the command line (terminal) - are there any warnings/errors when it crashes?

[JoeCFD]

I have bee using Qt Creator 16.0.0 daily on Ubuntu 22.04 for some time and have not experienced any crash. Can you repeat the crash?

[mithune0000]

I get something like but if opening from terminal its not crashing when editing cpp files.

Warning: Ignoring WAYLAND_DISPLAY on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
qt.accessibility.atspi: Could not find accessible on path: "/org/a11y/atspi/accessible/2147484458"

[JoeCFD]

@mithune0000 I see. It could be wayland related. I have Xorg and do not have crash issue.

Can you try:
export QT_ACCESSIBILITY=0
export QT_QPA_PLATFORM=wayland
then start qt creator

Wait. You said no issues when qt creator is launched from command line, right? How do you launch it when it crashes?

[mithune0000]

It did not crash for a while when ran from terminal but started crashing. Previously, I was using app icon to open

Steps:

1. I opened main.cpp, it worked fine but when opened one of my project's cpp files it crashed.
2. Trying to open again using ./qtcreator and then if trying to open default session it crashing with logs given

Failed to initialize instances shared memory:  "QSharedMemory::handle: doesn't exist"
qt.accessibility.atspi: Could not find accessible on path: "/org/a11y/atspi/accessible/2147484457"
QTextCursor::setPosition: Position '338' out of range
QTextCursor::setPosition: Position '338' out of range
QTextCursor::setPosition: Position '338' out of range
QTextCursor::setPosition: Position '338' out of range
qt.accessibility.atspi: Could not find accessible on path: "/org/a11y/atspi/accessible/2147484534"
qt.accessibility.atspi: Could not find accessible on path: "/org/a11y/atspi/accessible/2147484999"
QTextCursor::setPosition: Position '716' out of range
QTextCursor::setPosition: Position '716' out of range
QTextCursor::setPosition: Position '716' out of range
QTextCursor::setPosition: Position '716' out of range
QTextCursor::setPosition: Position '716' out of range
QTextCursor::setPosition: Position '716' out of range
QTextCursor::setPosition: Position '716' out of range
QTextCursor::setPosition: Position '716' out of range
qtc.qmljs.common: missing template type for registrationFunction  3
qtc.qmljs.common: missing template type for registrationFunction  3
qtc.qmljs.common: missing template type for registrationFunction  3
qtc.qmljs.common: missing template type for registrationFunction  3
qtc.qmljs.common: missing template type for registrationFunction  3
qtc.qmljs.common: missing template type for registrationFunction  3
qtc.qmljs.common: missing template type for registrationFunction  3
qt.accessibility.atspi: Could not find accessible on path: "/org/a11y/atspi/accessible/2147485043"
[1]    189835 segmentation fault (core dumped)  ./qtcreator

[JoeCFD]

Can you try?
export QT_LINUX_ACCESSIBILITY_ALWAYS_ON=0
./qtcreator

[mithune0000]

@JoeCFD I find no luck setting export QT_LINUX_ACCESSIBILITY_ALWAYS_ON=0 and starting the qt creator. Its crashing with segmentation fault.

[aha_1980]

@mithune0000 Can you start QtCreator from gdb and get a the stack trace?

That would be helpful for creating a bugreport so the developers can have a look.

Thanks and regards

[mithune0000]

@aha_1980 I might be asking very naive question, please forgive me for that. From gdb did you mean apply any settings in this screen and then run ./qtcreator ? Or can I run using some arguments to qtcreator which will provide debug logs?

[aha_1980]

@mithune0000

No, I meant to run from a terminal gdb /path/to/qtcreator and then let qtcreator run (type run in the gdb console) until it crashes. From there, you can request a stack trace (called backtrace in gdb) which could give some more insight why it is crashing.

[mithune0000]

@aha_1980 This is what I have found, does it help ?

Thread 1 "qtcreator" received signal SIGSEGV, Segmentation fault.
0x00007ffff69f8d94 in ?? () from /home/mithun/Qt6.9/Tools/QtCreator/bin/../lib/Qt/lib/libQt6Gui.so.6
(gdb) backtrace
#0  0x00007ffff69f8d94 in ??? () at /home/mithun/Qt6.9/Tools/QtCreator/bin/../lib/Qt/lib/libQt6Gui.so.6
#1  0x00007ffff69fbd25 in ??? () at /home/mithun/Qt6.9/Tools/QtCreator/bin/../lib/Qt/lib/libQt6Gui.so.6
#2  0x00007ffff6a03428 in ??? () at /home/mithun/Qt6.9/Tools/QtCreator/bin/../lib/Qt/lib/libQt6Gui.so.6
#3  0x00007ffff5f7d47a in ??? () at /home/mithun/Qt6.8/6.8.2/gcc_64/lib/libQt6DBus.so.6
#4  0x00007ffff5f80952 in ??? () at /home/mithun/Qt6.8/6.8.2/gcc_64/lib/libQt6DBus.so.6
#5  0x00007ffff59d1668 in QObject::event(QEvent*) () at /home/mithun/Qt6.9/Tools/QtCreator/bin/../lib/Qt/lib/libQt6Core.so.6
#6  0x00007ffff71907a6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /home/mithun/Qt6.9/Tools/QtCreator/bin/../lib/Qt/lib/libQt6Widgets.so.6
#7  0x00007ffff597bc32 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /home/mithun/Qt6.9/Tools/QtCreator/bin/../lib/Qt/lib/libQt6Core.so.6
#8  0x00007ffff597f1ad in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /home/mithun/Qt6.9/Tools/QtCreator/bin/../lib/Qt/lib/libQt6Core.so.6
#9  0x00007ffff5c584c7 in ??? () at /home/mithun/Qt6.9/Tools/QtCreator/bin/../lib/Qt/lib/libQt6Core.so.6
#10 0x00007ffff5710397 in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x00007ffff5770dc7 in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x00007ffff570f8b3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x00007ffff5c57b8e in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /home/mithun/Qt6.9/Tools/QtCreator/bin/../lib/Qt/lib/libQt6Core.so.6
#14 0x00007ffff598830b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /home/mithun/Qt6.9/Tools/QtCreator/bin/../lib/Qt/lib/libQt6Core.so.6
#15 0x00007ffff59842f6 in QCoreApplication::exec() () at /home/mithun/Qt6.9/Tools/QtCreator/bin/../lib/Qt/lib/libQt6Core.so.6
#16 0x000000000041034f in ??? ()
#17 0x00007ffff502a3b8 in __libc_start_call_main (main=main@entry=0x40c490, argc=argc@entry=1, argv=argv@entry=0x7fffffffdb48) at ../sysdeps/nptl/libc_start_call_main.h:58
#18 0x00007ffff502a47b in __libc_start_main_impl
    (main=0x40c490, argc=1, argv=0x7fffffffdb48, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffdb38) at ../csu/libc-start.c:360
#19 0x0000000000410a0e in ??? ()

[aha_1980]

@mithune0000 Yes, that's what I wanted to see. Please create a report at bugreports.qt.io and append this trace.

Thanks!

[Christian Ehrlicher]

@mithune0000 said in Qt Creator 16.0.0 is crashing when opening cpp files:

#2 0x00007ffff6a03428 in ??? () at /home/mithun/Qt6.9/Tools/QtCreator/bin/../lib/Qt/lib/libQt6Gui.so.6
#3 0x00007ffff5f7d47a in ??? () at /home/mithun/Qt6.8/6.8.2/gcc_64/lib/libQt6DBus.so.6

As you can see there is a mixture of different Qt versions. Fix your LD_LIBRARY_PATH so that te correct (Qt6.9) Qt libs are always loaded.

[mithune0000]

Few things I observed in the stack trace -

1. From Qt6.9 its going and running libraries from Qt6.8 may be because I have env vars set in ~/.zshrc

#3  0x00007ffff5f7d47a in ??? () at /home/mithun/Qt6.8/6.8.2/gcc_64/lib/libQt6DBus.so.6
#4  0x00007ffff5f80952 in ??? () at /home/mithun/Qt6.8/6.8.2/gcc_64/lib/libQt6DBus.so.6

ENV vars

export PATH=$PATH:/home/mithun/Qt6.8/6.8.2/gcc_64/bin
export CMAKE_PREFIX_PATH=/home/mithun/Qt6.8/6.8.2/gcc_64:$CMAKE_PREFIX_PATH
export LD_LIBRARY_PATH=/home/mithun/Qt6.8/6.8.2/gcc_64/lib:$LD_LIBRARY_PATH
export QT_PLUGIN_PATH=/home/mithun/Qt6.8/6.8.2/gcc_64/plugins
export QML2_IMPORT_PATH=/home/mithun/Qt6.8/6.8.2/gcc_64/qml

Now, I changed the env vars to point to Qt6.9 and tried running gdb ./qtcreator, then I am getting following error /home/mithun/Qt6.9/Tools/QtCreator/bin/qtcreator: /home/mithun/Qt6.9/Tools/QtCreator/bin/../lib/Qt/lib/libQt6Core.so.6: version 'Qt_6.9' not found (required by /home/mithun/Qt6.9/6.9.0/gcc_64/lib/libQt6DBus.so.6)

export PATH=$PATH:/home/mithun/Qt6.9/6.9.0/gcc_64/bin
export CMAKE_PREFIX_PATH=/home/mithun/Qt6.9/6.9.0/gcc_64:$CMAKE_PREFIX_PATH
export LD_LIBRARY_PATH=/home/mithun/Qt6.9/6.9.0/gcc_64/lib:$LD_LIBRARY_PATH
export QT_PLUGIN_PATH=/home/mithun/Qt6.9/6.9.0/gcc_64/plugins
export QML2_IMPORT_PATH=/home/mithun/Qt6.9/6.9.0/gcc_64/qml

[Christian Ehrlicher]

Don't set any LD_LIBRARY_PATH globally - you must not mix up different Qt versions or installations and it only makes trouble (as you can see).

[mithune0000]

@Christian-Ehrlicher I tried few options -

• Remove LD_LIBRARY_PATH, source zshrc and run qt creator.

• Remove all the envs related to Qt, source zshrc and run

Still getting the same error /home/mithun/Qt6.9/Tools/QtCreator/bin/qtcreator: /home/mithun/Qt6.9/Tools/QtCreator/bin/../lib/Qt/lib/libQt6Core.so.6: version 'Qt_6.9' not found (required by /home/mithun/Qt6.9/6.9.0/gcc_64/lib/libQt6DBus.so.6)

Can it happen that during Qt installation, these path are set and now removing from zshrc is not taking the effect ?

[ziller]

You have to either close and reopen the terminal to make any removal of environment variables from zshrc effective, or need to "unset LD_LIBRARY_PATH" in that terminal/shell manually.

[mithune0000]

Even after fixing the LD_LIBRARY_PATH, its crashing

Thread 1 "qtcreator" received signal SIGSEGV, Segmentation fault.
0x00007ffff69f8d94 in ?? () from /home/mithun/Qt6.9/Tools/QtCreator/bin/../lib/Qt/lib/libQt6Gui.so.6
(gdb) backtrace
#0  0x00007ffff69f8d94 in ??? () at /home/mithun/Qt6.9/Tools/QtCreator/bin/../lib/Qt/lib/libQt6Gui.so.6
#1  0x00007ffff69fbd25 in ??? () at /home/mithun/Qt6.9/Tools/QtCreator/bin/../lib/Qt/lib/libQt6Gui.so.6
#2  0x00007ffff6a03428 in ??? () at /home/mithun/Qt6.9/Tools/QtCreator/bin/../lib/Qt/lib/libQt6Gui.so.6
#3  0x00007ffff5f7d47a in ??? () at /home/mithun/Qt6.9/Tools/QtCreator/bin/../lib/Qt/lib/libQt6DBus.so.6
#4  0x00007ffff5f80952 in ??? () at /home/mithun/Qt6.9/Tools/QtCreator/bin/../lib/Qt/lib/libQt6DBus.so.6
#5  0x00007ffff59d1668 in QObject::event(QEvent*) () at /home/mithun/Qt6.9/Tools/QtCreator/bin/../lib/Qt/lib/libQt6Core.so.6
#6  0x00007ffff71907a6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /home/mithun/Qt6.9/Tools/QtCreator/bin/../lib/Qt/lib/libQt6Widgets.so.6
#7  0x00007ffff597bc32 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /home/mithun/Qt6.9/Tools/QtCreator/bin/../lib/Qt/lib/libQt6Core.so.6
#8  0x00007ffff597f1ad in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /home/mithun/Qt6.9/Tools/QtCreator/bin/../lib/Qt/lib/libQt6Core.so.6
#9  0x00007ffff5c584c7 in ??? () at /home/mithun/Qt6.9/Tools/QtCreator/bin/../lib/Qt/lib/libQt6Core.so.6
#10 0x00007ffff5710397 in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x00007ffff5770dc7 in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x00007ffff570f8b3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x00007ffff5c57b8e in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /home/mithun/Qt6.9/Tools/QtCreator/bin/../lib/Qt/lib/libQt6Core.so.6
#14 0x00007ffff598830b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /home/mithun/Qt6.9/Tools/QtCreator/bin/../lib/Qt/lib/libQt6Core.so.6
#15 0x00007ffff59842f6 in QCoreApplication::exec() () at /home/mithun/Qt6.9/Tools/QtCreator/bin/../lib/Qt/lib/libQt6Core.so.6
#16 0x000000000041034f in ??? ()
#17 0x00007ffff502a3b8 in __libc_start_call_main (main=main@entry=0x40c490, argc=argc@entry=1, argv=argv@entry=0x7fffffffdc98) at ../sysdeps/nptl/libc_start_call_main.h:58
#18 0x00007ffff502a47b in __libc_start_main_impl
    (main=0x40c490, argc=1, argv=0x7fffffffdc98, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffdc88) at ../csu/libc-start.c:360
#19 0x0000000000410a0e in ??? ()

[Christian Ehrlicher]

Then please install the debug symbols for QtCreator (through the maintainance tool) so the backtrace is more useful. Thx.

[JoeCFD]

Maybe switch to Xorg and try it out as well to see if there is any crash. If not, file a bug report specifically for Wayland.