Bug 183269 - The application Dolphin (dolphin) crashed and caused the signal 6 (SIGABRT)
Summary: The application Dolphin (dolphin) crashed and caused the signal 6 (SIGABRT)
Status: RESOLVED FIXED
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-05 08:32 UTC by Barco
Modified: 2011-02-27 20:11 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 4.7.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Barco 2009-02-05 08:32:18 UTC
Version:           1.1 (using KDE 4.1.3)
OS:                Linux
Installed from:    Fedora RPMs

It crashed when I tried to open some file or folders.

Error details:
Application: Dolphin (dolphin), signal SIGABRT
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb7f54770 (LWP 7963)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0x00110416 in __kernel_vsyscall ()
#7  0x002f4460 in raise () from /lib/libc.so.6
#8  0x002f5e28 in abort () from /lib/libc.so.6
#9  0x002ed40e in __assert_fail () from /lib/libc.so.6
#10 0x0027a496 in Strigi::SubInputStream::read ()
   from /usr/lib/libstreams.so.0
#11 0x0026a15c in Strigi::DataEventInputStream::read ()
   from /usr/lib/libstreams.so.0
#12 0x02608a87 in ?? () from /usr/lib/libstreamanalyzer.so.0
#13 0x025d9b5e in Strigi::AnalysisResult::indexChild ()
   from /usr/lib/libstreamanalyzer.so.0
#14 0x02619760 in ?? () from /usr/lib/libstreamanalyzer.so.0
#15 0x02619e5b in ?? () from /usr/lib/libstreamanalyzer.so.0
#16 0x02608b6f in ?? () from /usr/lib/libstreamanalyzer.so.0
#17 0x037a543e in ?? () from /usr/lib/libkio.so.5
#18 0x037a7195 in KFileMetaInfo::KFileMetaInfo () from /usr/lib/libkio.so.5
#19 0x0807ed14 in _start ()
Comment 1 Peter Penz 2009-02-05 08:43:38 UTC
Thanks for the report. Judging from the info of the backtrace it seems that the crash occured due to hovering a specific file because of a strigi issue (strigi is used to show the meta information of the file in the information panel). Would it be possible that you let us know which kind of file you wanted to open? I'm quite sure the issue should be reproducible with this specific file type in your system...

PS: more infos about backtraces are available at http://techbase.kde.org/index.php?title=Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Comment 2 Peter Penz 2009-02-05 09:06:24 UTC
Got a private mail from Barco:

"Hi Peter,

Thank you for quick response!
When I tried to open files of Microsoft Power Point (.ppt), the Dolphin crashed."

I've submitted a strigi bug report at http://sourceforge.net/tracker/index.php?func=detail&atid=856302&aid=2567315&group_id=171000
Comment 3 phreedom.stdin 2010-08-26 00:25:24 UTC
I definitely need a copy of the file to fix this bug
Comment 4 Peter Penz 2011-02-27 20:11:37 UTC
Git commit d1254968eac95f4d9d8c47552e27f0cc40e6aed9 by Peter Penz.
Committed on 27/02/2011 at 20:01.
Pushed by ppenz into branch 'master'.

KFileMetaDataProvider: Don't crash if a Strigi analyzer crashes

Some Strigi analyzers are still unstable and crash under certain circumstances. This patch moves the reading of the meta-data into a custom process instead of doing it in a thread, which assures that a crashing Strigi analyzer does not result in crashing Dolphin or Konqueror when hovering some items.

FIXED-IN: 4.7.0
BUG: 257964
BUG: 258715
BUG: 262299
BUG: 263468
BUG: 263502
BUG: 264254
BUG: 234799
BUG: 251462
BUG: 251701
BUG: 258918
BUG: 192377
BUG: 195564
BUG: 199368
BUG: 210841
BUG: 245376
BUG: 246461
BUG: 246901
BUG: 249150
BUG: 261952
BUG: 249876
BUG: 179376
BUG: 179417
BUG: 179420
BUG: 181591
BUG: 183269
BUG: 183722
BUG: 185667
BUG: 188596
BUG: 191864
BUG: 193112
BUG: 205813
BUG: 244621
BUG: 245451
BUG: 248214
BUG: 249655
BUG: 249876
BUG: 265549
BUG: 267079

M  +11   -1    kio/CMakeLists.txt     
M  +68   -38   kio/kfile/kfilemetadataprovider.cpp     
M  +2    -1    kio/kfile/kfilemetadataprovider_p.h     
A  +174  -0    kio/kfile/kfilemetadatareader.cpp         [License: LGPL (v2+)]
M  +0    -2    kio/kfile/kfilemetadatawidget.cpp     
D  +0    -178  kio/kfile/kloadfilemetadatathread.cpp     
D  +0    -96   kio/kfile/kloadfilemetadatathread_p.h     

http://commits.kde.org/kdelibs/d1254968eac95f4d9d8c47552e27f0cc40e6aed9