Re: Help with debugging a bug in Konqueror
Jure Repinc <[email protected]> Tue, 14 Jul 2026 10:41:14 +0200
| Newsgroups | gmane.comp.kde.devel.general |
|---|---|
| Organization | Holodeck 1 |
| Message-ID | <[email protected]> |
--nextPartqpmAQEDHTsqjzNonkRg_3A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8"; protected-headers="v1" From: Jure Repinc <[email protected]> To: [email protected] Subject: Re: Help with debugging a bug in Konqueror Date: Tue, 14 Jul 2026 10:41:14 +0200 Message-ID: <[email protected]> Organization: Holodeck 1 In-Reply-To: <[email protected]> MIME-Version: 1.0 Dne torek, 14. julij 2026 ob 08:36 je Stefano Crocco napisal(a): > On luned=C3=AC 13 luglio 2026 23:21:13 Ora legale dell=E2=80=99Europa cen= trale Albert >=20 > Astals Cid wrote: > > El dilluns, 13 de juliol del 2026, a les 9:39:58 (Hora d=E2=80=99estiu = d=E2=80=99Europa > >=20 > > central), Stefano Crocco va escriure: > > > On luned=C3=AC 13 luglio 2026 08:49:46 Ora legale dell=E2=80=99Europa= centrale you >=20 > wrote: > > > > On Mon, 2026-07-13 at 08:41 +0200, Stefano Crocco wrote: > > > > > Hello to everyone, > > > > > for the last few weeks, I've randomly encountered what I assume i= s a > > > > > bug in > > > > > Konqueror: I'd like to fix it, because it's rather annoying, but I > > > > > don't know > > > > > how to debug it to find its cause. > > > > >=20 > > > > > The issue is that sometimes Konqueror completely freezes: none of > > > > > its > > > > > windows > > > > > respond to mouse or keyboard. The only way to go on is to kill it. > > > > > It's not a > > > > > frequent issue: it usually happens once a day or so. Once it has > > > > > happened, > > > > > however, it's likely to happen again in a short time. > > > > >=20 > > > > > I attach a backtrace by attaching gdb to the Konqueror instance o= nce > > > > > the > > > > > freeze happens. As you can see, it contains almost nothing from > > > > > Konqueror > > > > > itself: just two calls near the bottom, the last of which is a ca= ll > > > > > to > > > > > QApplication::exec(). All other function calls are either inside = KDE > > > > > Frameworks or Qt: I'd almost think this is not a problem with > > > > > Konqueror if it > > > > > were not for the fact that I'm only experiencing the issue with > > > > > Konqueror. > > > >=20 > > > > Are you sure freeze happens in that thread? > > > >=20 > > > > The stacktrace is from the rendering thread. Does Konqueror window = get > > > > "grayed out" by KWin when it freezes? If it doesn't I'd think the > > > > freeze happens in another thread. > > >=20 > > > Thanks for the answer. No, the Konqueror window doesn't look grayed > > > out: > > > it looks completely normal to the point that often I don't realize it > > > has > > > frozen until I try to interact with: only at that point I notice that > > > all > > > parts of the UI don't respond in any way yo mouse or keyboard. If I > > > minimize the window, then restore it, its contents aren't drawn so th= at > > > it shows the contents of the previously active window. > > >=20 > > > > > Given the randomness of the freezes and the fact that the backtra= ce > > > > > contains > > > > > almost no Konqueror-specific calls, I really have no ideas on how= to > > > > > proceed to > > > > > debug the issue, and I really don't even know what to search on t= he > > > > > web. Do > > > > > you have any advice? > > > > >=20 > > > > > Thanks in advance > > > > >=20 > > > > > Stefano > > >=20 > > > I attach a new backtrace with all threads (compressed because of size= ). > > > I > > > still can't see anything related to Konqueror. The only thing I can > > > notice > > > is a mention of QDBus in thread 67, but I still don't know what > > > information > > > to get from it. Any other ideas? > >=20 > > Does it always get stuck in glXSwapBuffers ? > >=20 > > That would call for a driver bug possibly? > >=20 > > Does using > >=20 > > export QT_XCB_FORCE_SOFTWARE_OPENGL=3D1 > >=20 > > make it not get stuck? > >=20 > > Cheers, > >=20 > > Albert >=20 > Thanks for the avice. I've kept the backtraces of three of these situatio= ns > and all of them show a call to glXSwapBuffers. As soon as I have time, I'= ll > try your suggestion about QT_XCB_FORCE_SOFTWARE_OPENGL even if I fear it > would be difficult to determine whether it actually prevents the issue, > given its randomness. For example, yesterday morning I experienced it > several times but I haven't had it since yesterday afternoon. >=20 > Stefano I have recently been experiencing the same freezes and I stumbled upon thos= e=20 two bug reports in Mesa 3D that may be related to this: https://gitlab.freedesktop.org/mesa/mesa/-/work_items/15765 https://gitlab.freedesktop.org/mesa/mesa/-/work_items/15802 There is already some merge request merged that might fix it. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/42758 Will compile Mesa from git and see if it works for my Falkon freezes. Have a great time, Jure =2D-=20 Jabber/XMPP: [email protected] Matrix: @jlp:matrix.org Mastodon/ActivityPub: @[email protected] =20 --nextPartqpmAQEDHTsqjzNonkRg_3A Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iHgEABECADkWIQSu82KB/sp8mYwGoEB7KpNXGRqc9wUCalX2KhsUgAAAAAAEAA5t YW51MiwyLjUrMS4xMiwyLDIACgkQeyqTVxkanPdoawCdHHQ7kOMe4pEoc8io+WuV 8OHpzocAlA7JPI8o2X6I6D6ZZnQmrimdHSU= =f3ul -----END PGP SIGNATURE----- --nextPartqpmAQEDHTsqjzNonkRg_3A--