Bug 354217

Summary:	Please deploy bugzilla-traceparser on our install
Product:	[Websites] bugs.kde.org	Reporter:	Martin Klapetek <mklapetek>
Component:	general	Assignee:	KDE sysadmins <sysadmin>
Status:	CONFIRMED ---
Severity:	wishlist	CC:	kde, nate, sheedy
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=227502
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Martin Klapetek 2015-10-22 16:06:47 UTC

It's not unusual that Plasma runs with about 50 threads. Triaging Plasma crashes is very hard because people always post the full backtrace which is loooooong. This constant searching (and scrolling) in those backtraces is limiting productivity when bug triaging.

Couple examples: bug 339211 bug 342763 bug 345397

Therefore I'd like to request to deploy this on our bugzilla:
https://launchpad.net/bugzilla-traceparser

It brings many features very useful for dealing with backtraces, especially long ones like Plasma has. The main features are highlighted right on that page, but in short: hides non-interesting bt pieces, hides them by default (using js I presume), better duplicate searching and auto-duplicate features.

It also creates a report about the most reported backtraces, which I think can be useful to identify our most crashy bits.

Comment 1 Kai Uwe Broulik 2015-10-23 19:16:22 UTC

I like that. It has even ocurred that I wasn't able to submit a bugreport through DrKonqi because the backtrace was too long for the comments section.

Comment 2 Justin Zobel 2021-03-09 05:49:39 UTC

Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.

Comment 3 Martin Klapetek 2021-03-09 19:09:50 UTC

This report is still valid, yes.