Summary: | Kontact Crashed after attempting to add a large file as an attachment | ||
---|---|---|---|
Product: | [Applications] kontact | Reporter: | Jussi Schultink <jussi01> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | dev+kde, kdenis |
Priority: | NOR | ||
Version: | 4.10.1 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Jussi Schultink
2013-04-05 06:54:23 UTC
Created attachment 99218 [details]
New crash information added by DrKonqi
kontact (4.14.10) on KDE Platform 4.14.16 using Qt 4.8.6
- What I was doing when the application crashed:
I aimed for a PNG in the file dialog, but hit a 5 GiB VirtualBox image instead. :o) I only though “oops” and two seconds later KMail crashed.
-- Backtrace (Reduced):
#6 0x00007f68aff7c521 in QByteArray::append (this=0x2accb18, ba=...) at /var/tmp/portage/dev-qt/qtcore-4.8.6-r2/work/qt-everywhere-opensource-src-4.8.6/src/corelib/tools/qbytearray.cpp:1619
[...]
#8 0x00007f68ae0035a4 in KIO::TransferJob::data (this=this@entry=0x2b62890, _t1=_t1@entry=0x2b62890, _t2=...) at /var/tmp/portage/kde-base/kdelibs-4.14.16/work/kdelibs-4.14.16_build/kio/jobclasses.moc:446
#9 0x00007f68ae0065a9 in KIO::TransferJob::slotData (this=0x2b62890, _data=...) at /var/tmp/portage/kde-base/kdelibs-4.14.16/work/kdelibs-4.14.16/kio/kio/job.cpp:999
[...]
#11 0x00007f68ae0b1d42 in KIO::SlaveInterface::data (this=this@entry=0x16905d0, _t1=...) at /var/tmp/portage/kde-base/kdelibs-4.14.16/work/kdelibs-4.14.16_build/kio/slaveinterface.moc:159
#12 0x00007f68ae0b395a in KIO::SlaveInterface::dispatch (this=0x16905d0, _cmd=100, rawdata=...) at /var/tmp/portage/kde-base/kdelibs-4.14.16/work/kdelibs-4.14.16/kio/kio/slaveinterface.cpp:164
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those Framework-based versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input. |