Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#918410: [qtcreator] qtcreator freezes during startup
98 views
Skip to first unread message
Johannes Zarl-Zierl
Jan 5, 2019, 4:00:03 PM1/5/19
to
Package: qtcreator
Version: 4.8.0-1
Severity: normal
--- Please enter the report below this line. ---
After upgrading to qtcreator 4.8.0-1, I experience qtcreator reproducibly
"freezing" during startup.
Starting qtcreator using "qtcreator -profile" revealed that the "Help" module
is the last one that is loaded so I tried starting qtcreator with "-noload
Help" and it starts correctly. In that case I do get a segfault later on when
I quit qtcreator, but that's probably unrelated.
I also use some of the Clang related plugins (just mentioning this in case it
might be relevant).
Cheers,
Johannes
--- System information. ---
Architecture:
Kernel: Linux 4.19.0-1-amd64
Debian Release: buster/sid
500 unstable ftp.at.debian.org
--- Package information. ---
Depends (Version) | Installed
============================================================-+-
=============================
libqt5sql5-sqlite | 5.11.3+dfsg-2
qml-module-qtqml-models2 | 5.11.3-2
qml-module-qtquick-controls (>= 5.5.0~) | 5.11.3-2
qml-module-qtquick2 (>= 5.5.0~) | 5.11.3-2
qtchooser | 66-1
qtcreator-data (= 4.8.0-1) | 4.8.0-1
libbotan-2-5 | 2.6.0-3
libc6 (>= 2.28) |
libclang1-7 (>= 1:7~svn334604-1~exp1+0~) |
libgcc1 (>= 1:3.0) |
libgl1 |
libllvm7 (>= 1:7~svn298832-1~) |
libqbscore1.12 (>= 1.12.0) |
libqbsqtprofilesetup1.12 (>= 1.2.1) |
libqt5concurrent5 (>= 5.6.2~) |
libqt5core5a (>= 5.11.0~rc1) |
libqt5designer5 (>= 5.6.2~) |
libqt5designercomponents5 (>= 5.6.2~) |
libqt5gui5 (>= 5.8.0) |
libqt5help5 (>= 5.9.0) |
libqt5network5 (>= 5.6.2~) |
libqt5printsupport5 (>= 5.6.2~) |
libqt5qml5 (>= 5.1.0) |
libqt5quick5 (>= 5.9.0~beta) |
libqt5quickwidgets5 (>= 5.11.0) |
libqt5script5 (>= 5.6.0~beta) |
libqt5serialport5 (>= 5.9.0) |
libqt5sql5 (>= 5.6.2~) |
libqt5widgets5 (>= 5.11.0~rc1) |
libqt5xml5 (>= 5.6.2~) |
libstdc++6 (>= 7) |
qtbase-abi-5-11-3 |
qtdeclarative-abi-5-11-2 |
Recommends (Version) | Installed
=======================================-+-===========
clang | 1:7.0-47
gdb | 8.2-1
make | 4.2.1-1.2
qmlscene | 5.11.3-2
qt5-doc | 5.11.3-1
qt5-qmltooling-plugins | 5.11.3-2
qtbase5-dev-tools | 5.11.3+dfsg-2
qtcreator-doc | 4.8.0-1
qtdeclarative5-dev-tools | 5.11.3-2
qttools5-dev-tools | 5.11.3-2
qttranslations5-l10n | 5.11.3-2
qtxmlpatterns5-dev-tools | 5.11.3-2
xterm | 341-1
OR x-terminal-emulator |
Suggests (Version) | Installed
=========================-+-===========
clazy |
cmake | 3.13.2-1
g++ | 4:8.2.0-2
git | 1:2.20.1-1
kate-data | 4:4.14.3-5
subversion | 1.10.3-1+b1
valgrind | 1:3.14.0-2
--
Johannes Zarl-Zierl
FSFE local group Linz, Team Austria
https://wiki.fsfe.org/LocalGroups/Linz_en/
Version: 4.8.0-1
Severity: normal
--- Please enter the report below this line. ---
After upgrading to qtcreator 4.8.0-1, I experience qtcreator reproducibly
"freezing" during startup.
Starting qtcreator using "qtcreator -profile" revealed that the "Help" module
is the last one that is loaded so I tried starting qtcreator with "-noload
Help" and it starts correctly. In that case I do get a segfault later on when
I quit qtcreator, but that's probably unrelated.
I also use some of the Clang related plugins (just mentioning this in case it
might be relevant).
Cheers,
Johannes
--- System information. ---
Architecture:
Kernel: Linux 4.19.0-1-amd64
Debian Release: buster/sid
500 unstable ftp.at.debian.org
--- Package information. ---
Depends (Version) | Installed
============================================================-+-
=============================
libqt5sql5-sqlite | 5.11.3+dfsg-2
qml-module-qtqml-models2 | 5.11.3-2
qml-module-qtquick-controls (>= 5.5.0~) | 5.11.3-2
qml-module-qtquick2 (>= 5.5.0~) | 5.11.3-2
qtchooser | 66-1
qtcreator-data (= 4.8.0-1) | 4.8.0-1
libbotan-2-5 | 2.6.0-3
libc6 (>= 2.28) |
libclang1-7 (>= 1:7~svn334604-1~exp1+0~) |
libgcc1 (>= 1:3.0) |
libgl1 |
libllvm7 (>= 1:7~svn298832-1~) |
libqbscore1.12 (>= 1.12.0) |
libqbsqtprofilesetup1.12 (>= 1.2.1) |
libqt5concurrent5 (>= 5.6.2~) |
libqt5core5a (>= 5.11.0~rc1) |
libqt5designer5 (>= 5.6.2~) |
libqt5designercomponents5 (>= 5.6.2~) |
libqt5gui5 (>= 5.8.0) |
libqt5help5 (>= 5.9.0) |
libqt5network5 (>= 5.6.2~) |
libqt5printsupport5 (>= 5.6.2~) |
libqt5qml5 (>= 5.1.0) |
libqt5quick5 (>= 5.9.0~beta) |
libqt5quickwidgets5 (>= 5.11.0) |
libqt5script5 (>= 5.6.0~beta) |
libqt5serialport5 (>= 5.9.0) |
libqt5sql5 (>= 5.6.2~) |
libqt5widgets5 (>= 5.11.0~rc1) |
libqt5xml5 (>= 5.6.2~) |
libstdc++6 (>= 7) |
qtbase-abi-5-11-3 |
qtdeclarative-abi-5-11-2 |
Recommends (Version) | Installed
=======================================-+-===========
clang | 1:7.0-47
gdb | 8.2-1
make | 4.2.1-1.2
qmlscene | 5.11.3-2
qt5-doc | 5.11.3-1
qt5-qmltooling-plugins | 5.11.3-2
qtbase5-dev-tools | 5.11.3+dfsg-2
qtcreator-doc | 4.8.0-1
qtdeclarative5-dev-tools | 5.11.3-2
qttools5-dev-tools | 5.11.3-2
qttranslations5-l10n | 5.11.3-2
qtxmlpatterns5-dev-tools | 5.11.3-2
xterm | 341-1
OR x-terminal-emulator |
Suggests (Version) | Installed
=========================-+-===========
clazy |
cmake | 3.13.2-1
g++ | 4:8.2.0-2
git | 1:2.20.1-1
kate-data | 4:4.14.3-5
subversion | 1.10.3-1+b1
valgrind | 1:3.14.0-2
--
Johannes Zarl-Zierl
FSFE local group Linz, Team Austria
https://wiki.fsfe.org/LocalGroups/Linz_en/
Bernhard Übelacker
Jan 6, 2019, 7:10:03 PM1/6/19
to
Hello Johannes,
thanks for your fast respone.
Can you repeat that gdb command with following additional
dbgsym packages installed, to complete the backtraces:
libxcb1-dbgsym libqt5gui5-dbgsym libqt5widgets5-dbgsym libqt5gui5-dbgsym libqt5dbus5-dbgsym libqt5core5a-dbgsym libglib2.0-0-dbgsym libgl1-mesa-dri-dbgsym libqt5qml5-dbgsym
As an distant observer I cannot say if the "clang code model"
thing deserves its own separate bug, has to be better decided by
the package maintainers...
If it shows up just sometimes you probably can describe your
cpu and number of cores?
Is it hanging too, if you start qtcreator with following command:
taskset -c 0 qtcreator
Kind regards,
Bernhard
thanks for your fast respone.
Can you repeat that gdb command with following additional
dbgsym packages installed, to complete the backtraces:
libxcb1-dbgsym libqt5gui5-dbgsym libqt5widgets5-dbgsym libqt5gui5-dbgsym libqt5dbus5-dbgsym libqt5core5a-dbgsym libglib2.0-0-dbgsym libgl1-mesa-dri-dbgsym libqt5qml5-dbgsym
As an distant observer I cannot say if the "clang code model"
thing deserves its own separate bug, has to be better decided by
the package maintainers...
If it shows up just sometimes you probably can describe your
cpu and number of cores?
Is it hanging too, if you start qtcreator with following command:
taskset -c 0 qtcreator
Kind regards,
Bernhard
Johannes Zarl-Zierl
Jan 7, 2019, 3:20:05 PM1/7/19
to
Hello Bernhard,
Am Montag, 7. Jänner 2019, 01:00:13 CET schrieb Bernhard Übelacker:
> thanks for your fast respone.
You're welcome.
> Can you repeat that gdb command with following additional
> dbgsym packages installed, to complete the backtraces:
>
> libxcb1-dbgsym libqt5gui5-dbgsym libqt5widgets5-dbgsym libqt5gui5-dbgsym
> libqt5dbus5-dbgsym libqt5core5a-dbgsym libglib2.0-0-dbgsym
> libgl1-mesa-dri-dbgsym libqt5qml5-dbgsym
Of course. See the attached log.
> If it shows up just sometimes you probably can describe your
> cpu and number of cores?
It's an Intel core 2 quad core processor. (See attached cpuinfo)
> Is it hanging too, if you start qtcreator with following command:
>
> taskset -c 0 qtcreator
Yes.
Cheers,
Johannes
Am Montag, 7. Jänner 2019, 01:00:13 CET schrieb Bernhard Übelacker:
> thanks for your fast respone.
> Can you repeat that gdb command with following additional
> dbgsym packages installed, to complete the backtraces:
>
> libxcb1-dbgsym libqt5gui5-dbgsym libqt5widgets5-dbgsym libqt5gui5-dbgsym
> libqt5dbus5-dbgsym libqt5core5a-dbgsym libglib2.0-0-dbgsym
> libgl1-mesa-dri-dbgsym libqt5qml5-dbgsym
> If it shows up just sometimes you probably can describe your
> cpu and number of cores?
> Is it hanging too, if you start qtcreator with following command:
>
> taskset -c 0 qtcreator
Cheers,
Johannes
Bernhard Übelacker
Jan 8, 2019, 5:00:03 AM1/8/19
to
Hello Johannes,
On Mon, 07 Jan 2019 21:06:28 +0100 Johannes Zarl-Zierl <jz...@fsfe.org> wrote:
> Hello Bernhard,
>
> Am Montag, 7. Jänner 2019, 01:00:13 CET schrieb Bernhard Übelacker:
> > Can you repeat that gdb command with following additional
> > dbgsym packages installed, to complete the backtraces:
> ...
That may point to the direction of Xorg or the graphics driver.
Is there any related output from the 'dmesg' command,
or in ~/.xsession-errors, or /var/log/Xorg.0.log.
I found a nearly similar backtrace in [1].
Do you use ssh with X forwarding?
In any case could you try if the hang still shows up when you start
qtcreator with this environment from bug [1] set.
QT_XCB_NO_MITSHM=1 qtcreator
Or forward the output when started with this logging enabled:
QT_LOGGING_RULES=qt.qpa.xcb.debug=true qtcreator
Kind regards,
Bernhard
[1] https://bugreports.qt.io/browse/QTBUG-68783
On Mon, 07 Jan 2019 21:06:28 +0100 Johannes Zarl-Zierl <jz...@fsfe.org> wrote:
> Hello Bernhard,
>
> Am Montag, 7. Jänner 2019, 01:00:13 CET schrieb Bernhard Übelacker:
> > Can you repeat that gdb command with following additional
> > dbgsym packages installed, to complete the backtraces:
> Of course. See the attached log.
Unfortunately all threads seem to just wait.
That may point to the direction of Xorg or the graphics driver.
Is there any related output from the 'dmesg' command,
or in ~/.xsession-errors, or /var/log/Xorg.0.log.
I found a nearly similar backtrace in [1].
Do you use ssh with X forwarding?
In any case could you try if the hang still shows up when you start
qtcreator with this environment from bug [1] set.
QT_XCB_NO_MITSHM=1 qtcreator
Or forward the output when started with this logging enabled:
QT_LOGGING_RULES=qt.qpa.xcb.debug=true qtcreator
Kind regards,
Bernhard
[1] https://bugreports.qt.io/browse/QTBUG-68783
Bernhard Übelacker
Jan 9, 2019, 1:30:03 PM1/9/19
to
Hello Johannes, dear Maintainer,
tried to reproduce the hang here but just got
a NV4B and NV108, while your NVA5 is somewhere between,
and with both I did not get such a freeze ...
I fear I cannot help on this issue any deeper.
Maybe some Qt or Nouveau developer need to have a look.
Kind regards,
Bernhard
tried to reproduce the hang here but just got
a NV4B and NV108, while your NVA5 is somewhere between,
and with both I did not get such a freeze ...
I fear I cannot help on this issue any deeper.
Maybe some Qt or Nouveau developer need to have a look.
Kind regards,
Bernhard
Lisandro Damián Nicanor Pérez Meyer
Jan 9, 2019, 4:50:03 PM1/9/19
to
tag 918410 unreproducible moreinfo
thanks
Please try the following:
a) Try opening Creator in a new user (you can also move stuff in ~/.config/,
but that's more involved, as you have an rc file and more data inside
QtProject).
b) Open Qt Creator and go to Help → About plugins. Then be sure to disable
whatever plugin has "Clang" in it. Close Qt Creator and try again.
This can also be video related, in which Clang might be related too (X stuff
is built with it).
Note that I'm not saying that Clang is the culprit, but just suspecting this.
Cheers, Lisandro.
--
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/
thanks
Please try the following:
a) Try opening Creator in a new user (you can also move stuff in ~/.config/,
but that's more involved, as you have an rc file and more data inside
QtProject).
b) Open Qt Creator and go to Help → About plugins. Then be sure to disable
whatever plugin has "Clang" in it. Close Qt Creator and try again.
This can also be video related, in which Clang might be related too (X stuff
is built with it).
Note that I'm not saying that Clang is the culprit, but just suspecting this.
Cheers, Lisandro.
--
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/
Johannes Zarl-Zierl
Jan 9, 2019, 4:50:04 PM1/9/19
to
Hello Bernhard,
Am Mittwoch, 9. Jänner 2019, 19:19:04 CET schrieb Bernhard Übelacker:
> I fear I cannot help on this issue any deeper.
Thanks for your help! You enabled me to find a workaround for the immediate
issue, making the bug only a minor nuisance for me.
Cheers,
Johannes
Am Mittwoch, 9. Jänner 2019, 19:19:04 CET schrieb Bernhard Übelacker:
> I fear I cannot help on this issue any deeper.
issue, making the bug only a minor nuisance for me.
Cheers,
Johannes
Lisandro Damián Nicanor Pérez Meyer
Jan 9, 2019, 5:40:02 PM1/9/19
to
Can you tell us which exactly was? In this way:
- other users reading the report might benefit from it
- we might end up finding a proper solution
Thanks!
Johannes Zarl-Zierl
Jan 9, 2019, 6:10:02 PM1/9/19
to
Am Mittwoch, 9. Jänner 2019, 23:37:45 CET schrieb Lisandro Damián Nicanor
Pérez Meyer:
qtcreator does not freeze for me.
Johannes
P.S.: I did read your other mail regarding testing without clang-related
plugins under another user. Disabling those plugins under the same user does
not change anything. I hope I can test with a fresh user tomorrow…
Pérez Meyer:
> Can you tell us which exactly was? In this way:
>
> - other users reading the report might benefit from it
> - we might end up finding a proper solution
Sorry, I thought that was clear from the context. With QT_XCB_NO_MITSHM=1,
>
> - other users reading the report might benefit from it
> - we might end up finding a proper solution
qtcreator does not freeze for me.
Johannes
P.S.: I did read your other mail regarding testing without clang-related
plugins under another user. Disabling those plugins under the same user does
not change anything. I hope I can test with a fresh user tomorrow…
Lisandro Damián Nicanor Pérez Meyer
Jan 10, 2019, 3:30:02 PM1/10/19
to
El miércoles, 9 de enero de 2019 20:06:33 -03 Johannes Zarl-Zierl escribió:
> Am Mittwoch, 9. Jänner 2019, 23:37:45 CET schrieb Lisandro Damián Nicanor
>
> Pérez Meyer:
> > Can you tell us which exactly was? In this way:
> >
> > - other users reading the report might benefit from it
> > - we might end up finding a proper solution
>
> Sorry, I thought that was clear from the context. With QT_XCB_NO_MITSHM=1,
> qtcreator does not freeze for me.
And no ssh forwarding / X2Go, right?
> Am Mittwoch, 9. Jänner 2019, 23:37:45 CET schrieb Lisandro Damián Nicanor
>
> Pérez Meyer:
> > Can you tell us which exactly was? In this way:
> >
> > - other users reading the report might benefit from it
> > - we might end up finding a proper solution
>
> Sorry, I thought that was clear from the context. With QT_XCB_NO_MITSHM=1,
> qtcreator does not freeze for me.
>
> P.S.: I did read your other mail regarding testing without clang-related
> plugins under another user. Disabling those plugins under the same user does
> not change anything. I hope I can test with a fresh user tomorrow…
idea.
--
Los estadounidenses no tienen la culpa, la guerra tiene la culpa. La falta de
voluntad de la gente para comprender a aquellos que tienen valores diferentes,
eso es lo que tiene la culpa.
Shinji Mikamo
<http://www.lanacion.com.ar/1716475-el-cataclismo-nuclear-de-hiroshima-narrado-por-un-superviviente>
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.blogspot.com/
Johannes Zarl-Zierl
Jan 10, 2019, 4:40:02 PM1/10/19
to
Am Donnerstag, 10. Jänner 2019, 21:23:55 CET schrieb Lisandro Damián Nicanor
I also tested just now (in case qtcreator tries to communicate with ssh-agent
anyways) in a shell with SSH_AUTH_SOCK unset that the bug still appears.
> > P.S.: I did read your other mail regarding testing without clang-related
> > plugins under another user. Disabling those plugins under the same user
> > does not change anything. I hope I can test with a fresh user tomorrow…
> Please do. I can't reproduce the issue, so this will probably give us a
> better idea.
I just tested with a fresh user, and surprise: the bug does not appear!
This is with ClangCodeModel and ClangTools enabled (as per default), without
the QT_XCB_NO_MITSHM workaround.
This prompted me to move ~/.config/QtProject out of the way on my regular
account. This also worked. I then tried copying QtCreator.ini and QtCreator.db
back into the QtProject directory, and everything still works.
I also tried copying the toolchains/profiles/qtversion files back, but at that
point I realized that to do this correctly I would need more knowledge about
the internals than I have.
So, in summary:
1. *Something* in my ~/.config/QtProject folder caused the problem.
2. Starting with a fresh QtProject folder, the problem disappears.
3. I could salvage my QtCreator.ini without apparent problems (recreating my
kits is acceptable for me).
I guess this can be attributed to some cruft accumulating in my QtProject
folders over the years? If so, I guess it is fair to close this bug as
invalid/worksforme/whatever…
Thanks again,
Johannes
Pérez Meyer:
> El miércoles, 9 de enero de 2019 20:06:33 -03 Johannes Zarl-Zierl escribió:
> > Am Mittwoch, 9. Jänner 2019, 23:37:45 CET schrieb Lisandro Damián Nicanor
> >
> > Pérez Meyer:
> > > Can you tell us which exactly was? In this way:
> > >
> > > - other users reading the report might benefit from it
> > > - we might end up finding a proper solution
> >
> > Sorry, I thought that was clear from the context. With QT_XCB_NO_MITSHM=1,
> > qtcreator does not freeze for me.
>
> And no ssh forwarding / X2Go, right?
No ssh forwarding, and no X2Go. Everything runs local.
> El miércoles, 9 de enero de 2019 20:06:33 -03 Johannes Zarl-Zierl escribió:
> > Am Mittwoch, 9. Jänner 2019, 23:37:45 CET schrieb Lisandro Damián Nicanor
> >
> > Pérez Meyer:
> > > Can you tell us which exactly was? In this way:
> > >
> > > - other users reading the report might benefit from it
> > > - we might end up finding a proper solution
> >
> > Sorry, I thought that was clear from the context. With QT_XCB_NO_MITSHM=1,
> > qtcreator does not freeze for me.
>
> And no ssh forwarding / X2Go, right?
I also tested just now (in case qtcreator tries to communicate with ssh-agent
anyways) in a shell with SSH_AUTH_SOCK unset that the bug still appears.
> > P.S.: I did read your other mail regarding testing without clang-related
> > plugins under another user. Disabling those plugins under the same user
> > does not change anything. I hope I can test with a fresh user tomorrow…
> Please do. I can't reproduce the issue, so this will probably give us a
> better idea.
This is with ClangCodeModel and ClangTools enabled (as per default), without
the QT_XCB_NO_MITSHM workaround.
This prompted me to move ~/.config/QtProject out of the way on my regular
account. This also worked. I then tried copying QtCreator.ini and QtCreator.db
back into the QtProject directory, and everything still works.
I also tried copying the toolchains/profiles/qtversion files back, but at that
point I realized that to do this correctly I would need more knowledge about
the internals than I have.
So, in summary:
1. *Something* in my ~/.config/QtProject folder caused the problem.
2. Starting with a fresh QtProject folder, the problem disappears.
3. I could salvage my QtCreator.ini without apparent problems (recreating my
kits is acceptable for me).
I guess this can be attributed to some cruft accumulating in my QtProject
folders over the years? If so, I guess it is fair to close this bug as
invalid/worksforme/whatever…
Thanks again,
Johannes
0 new messages