[Bug 1140184] New: Falkon segfaults at exit, could be mesa related?
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184 Bug ID: 1140184 Summary: Falkon segfaults at exit, could be mesa related? Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs@opensuse.org Reporter: stakanov@freenet.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 809232 --> http://bugzilla.opensuse.org/attachment.cgi?id=809232&action=edit backtrace of the segfault, required libraries of falcon and mesa falkon did crash at exit with segfault. The installation of debug libraries does reveal a connection to Mesa (this is why I post it, konqi did not give an address to post so maybe this is not upstream. Feel free to point me upstream if applicable). The backtrace is joint with the attachment. Repeatable: well it crashed before, but is irregular, does not happen always. And this is the first time I get a usable backtrace. What the application does: segfaults What the application should do: should close without segfault. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184#c1
Wolfgang Bauer
Created attachment 809232 [details] backtrace of the segfault, required libraries of falcon and mesa
falkon did crash at exit with segfault. The installation of debug libraries does reveal a connection to Mesa (this is why I post it, konqi did not give an address to post so maybe this is not upstream. Feel free to point me upstream if applicable). Mesa is maintained by the X.Org team, reassigning.
FTR, it doesn't crash here, but I'm currently using Falkon 3.1.0 with Qt 5.13 on Leap 15.1 (with the default Mesa though, but an intel chip) I suppose setting the environment variable QT_WEBENGINE_DISABLE_GPU=1 (to force QtWebEngine to use software rendering instead) would help? E.g. run "QT_WEBENGINE_DISABLE_GPU=1 falkon", or add "QT_WEBENGINE_DISABLE_GPU=1" to /etc/environment and logout/login. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184#c2
Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184#c3
--- Comment #3 from Stakanov Schufter
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184#c4
Stakanov Schufter
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184#c5
--- Comment #5 from Stakanov Schufter
(In reply to Stakanov Schufter from comment #0)
Created attachment 809232 [details] backtrace of the segfault, required libraries of falcon and mesa
falkon did crash at exit with segfault. The installation of debug libraries does reveal a connection to Mesa (this is why I post it, konqi did not give an address to post so maybe this is not upstream. Feel free to point me upstream if applicable). Mesa is maintained by the X.Org team, reassigning.
FTR, it doesn't crash here, but I'm currently using Falkon 3.1.0 with Qt 5.13 on Leap 15.1 (with the default Mesa though, but an intel chip)
I suppose setting the environment variable QT_WEBENGINE_DISABLE_GPU=1 (to force QtWebEngine to use software rendering instead) would help? E.g. run "QT_WEBENGINE_DISABLE_GPU=1 falkon", or add "QT_WEBENGINE_DISABLE_GPU=1" to /etc/environment and logout/login.
I did try what you suggested. Substantially for now I see no difference (also because it is difficult as it does not crash so often, only "from time to time"). What triggered me to report was the fact that it wanted mesa debug libraries. I can set this as command of the start up of Falkon and see if on the long run it reproduces...or not. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184
Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184#c6
--- Comment #6 from Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184#c7
Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184#c8
Stakanov Schufter
Does it help to run falkon without GL_ATI_fragment_shader extension?
MESA_EXTENSION_OVERRIDE="-GL_ATI_fragment_shader" falkon
Well, as I said I cannot guarantee for the stability as crashes are irregular. With these settings I did not have a crash and what is weird the pages load as it seems faster. Actually much faster. Without there is always a stop of loading of about 1 second. With the setting the loading is immediate. That does of course not guarantee that this solves the problem but I like that it loads faster to tell the truth. Where can I force it to do this as "default" start settings, so to check if all is ok on the long run? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184#c9
--- Comment #9 from Wolfgang Bauer
Where can I force it to do this as "default" start settings, so to check if all is ok on the long run? As I wrote earlier, you could add it to /etc/environment e.g., i.e. edit the file in a text editor (as root) and in this case add the line: MESA_EXTENSION_OVERRIDE="-GL_ATI_fragment_shader"
Or maybe add this line to ~/.profile: export MESA_EXTENSION_OVERRIDE="-GL_ATI_fragment_shader" (it will only affect your user account then) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184#c10
--- Comment #10 from Stakanov Schufter
(In reply to Stakanov Schufter from comment #8)
Where can I force it to do this as "default" start settings, so to check if all is ok on the long run? As I wrote earlier, you could add it to /etc/environment e.g., i.e. edit the file in a text editor (as root) and in this case add the line: MESA_EXTENSION_OVERRIDE="-GL_ATI_fragment_shader"
Or maybe add this line to ~/.profile: export MESA_EXTENSION_OVERRIDE="-GL_ATI_fragment_shader" (it will only affect your user account then)
Well, done. If I do not complain it simply works. If not you are going have me reporting here again with backtrace. Thank you for the fast reply. Much appreciated. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184#c11
--- Comment #11 from Wolfgang Bauer
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184#c12
--- Comment #12 from Stakanov Schufter
Just to be sure: you shouldn't be using QT_WEBENGINE_DISABLE_GPU=1 now then, otherwise you'd probably avoid the problem by other means (as it should not use Mesa at all then)... ;-)
No, I did not use it. I only used the second solution as of my comments. The first one did not have a fastening effect (strange enough that it had). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184#c13
--- Comment #13 from Wolfgang Bauer
(In reply to Wolfgang Bauer from comment #11)
Just to be sure: you shouldn't be using QT_WEBENGINE_DISABLE_GPU=1 now then, otherwise you'd probably avoid the problem by other means (as it should not use Mesa at all then)... ;-)
No, I did not use it. I only used the second solution as of my comments. The first one did not have a fastening effect (strange enough that it had). Ok, I just wanted to mention it to avoid misunderstandings.
Btw, the first one (i.e. QT_WEBENGINE_DISABLE_GPU=1) was not supposed to speed up anything, it might even slow down things as the GPU is not used anymore for rendering at all... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184#c14
--- Comment #14 from Stakanov Schufter
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184#c15
--- Comment #15 from Stakanov Schufter
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184#c16
--- Comment #16 from Wolfgang Bauer
Created attachment 810494 [details] falcon segfaults at exit new backtrace
with the new settings.
Well, that's a completely different crash now.
Could you please report it upstream at bugs.kde.org against Falkon please?
Thanks.
The relevant backtrace now seems to be:
#6 QScopedPointer
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184
http://bugzilla.opensuse.org/show_bug.cgi?id=1140184#c21
Stakanov Schufter
participants (2)
-
bugzilla_noreply@novell.com
-
bugzilla_noreply@suse.com