Bug 271154 - KDE Bug reporting does not accept long stack traces because of 64k comment length limitation
Summary: KDE Bug reporting does not accept long stack traces because of 64k comment le...
Status: RESOLVED DUPLICATE of bug 248807
Alias: None
Product: drkonqi
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries FreeBSD
: NOR normal
Target Milestone: ---
Assignee: Dario Andres
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-17 14:20 UTC by Heikki Suonsivu
Modified: 2011-04-23 18:25 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Heikki Suonsivu 2011-04-17 14:20:02 UTC 
Version:           4.6 (using KDE 4.6.2) 
OS:                FreeBSD

Try filing a KDE bug report, which includes a > 64k long stack trace (generated by crash reporting tool), it says too long comments.  This seems rather counter-productive limitation.

Reproducible: Always

Steps to Reproduce:
Crash konqueror (this happened on www.hs.fi news site, when opening approximately 10 new tabs in the background).  It generated a crash, and crash reported generated a stack trace longer than 64k.


Actual Results:  
Error, too long comments, max 64k

Expected Results:  
Successful filing of a bug report.

64k might have been issue with software running on 8086 cpu.  That was 15-20 years ago.
Comment 1 Christoph Feck 2011-04-23 18:20:04 UTC 
I think the limitation is built into the bugs.kde.org server for a reason. But DrKonqi could cut off the backtrace, because such a long backtrace is likely caused by a recursion anyway.
Comment 2 George Kiagiadakis 2011-04-23 18:25:37 UTC 

*** This bug has been marked as a duplicate of bug 248807 ***