Bug 499677

Summary:	Plasma gets in crash loop when visiting a specific url in Firefox
Product:	[Plasma] plasmashell	Reporter:	Angelos <debiancat7>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED UNMAINTAINED
Severity:	crash	CC:	kde
Priority:	NOR	Keywords:	drkonqi
Version First Reported In:	5.27.5
Target Milestone:	1.0
Platform:	Debian stable
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	New crash information added by DrKonqi

Description Angelos 2025-02-08 11:50:08 UTC

Application: plasmashell (5.27.5)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.1.0-30-amd64 x86_64
Windowing System: X11
Distribution: Debian GNU/Linux 12 (bookworm)
DrKonqi: 5.27.5 [CoredumpBackend]

-- Information about the crash:
The bug is reproducable.

It happens when I visit https://fprime.jpl.nasa.gov/. It is in the crash loop until I close firefox, not just the tab. It does not happen in Chronium browser.

The crash can be reproduced every time.

-- Backtrace (Reduced):
#4  0x00007fa546c5a7b0 in QTextDocument::docHandle() const () at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#5  0x00007fa546c526b8 in QTextFrame::begin() const () at /lib/x86_64-linux-gnu/libQt5Gui.so.5
[...]
#8  0x00007fa546c966c0 in QTextDocumentLayout::doLayout(int, int, int) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#9  0x00007fa546c97a19 in QTextDocumentLayout::documentChanged(int, int, int) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#10 0x00007fa546c700b8 in QTextDocumentPrivate::clear() () at /lib/x86_64-linux-gnu/libQt5Gui.so.5


Reported using DrKonqi

Comment 1 Angelos 2025-02-08 11:50:08 UTC

Created attachment 178073 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

Comment 2 Bug Janitor Service 2025-02-08 12:33:39 UTC

Thank you for the bug report!

Debian advises users to not submit bugs upstream (https://www.debian.org/Bugs/Reporting), and Plasma 5.27.5 is no longer eligible for support or maintenance from KDE. It's possible that the issue exists only in Debian at this point.

Could you report the bug to Debian using the report bug utility (https://packages.debian.org/stable/utils/reportbug)? If necessary, the maintainer of the package will forward the bug upstream.
Thanks for understanding!

Thanks again!