Bug 255444 - konqueror crash listing CR2 RAW images
Summary: konqueror crash listing CR2 RAW images
Status: RESOLVED DUPLICATE of bug 250738
Alias: None
Product: konqueror
Classification: Applications
Component: file list view (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-27 22:24 UTC by Roman Fietze
Modified: 2010-12-12 20:41 UTC (History)
3 users (show)

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


Attachments
Backtrace (8.57 KB, text/plain)
2010-10-27 22:24 UTC, Roman Fietze
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Roman Fietze 2010-10-27 22:24:31 UTC
Created attachment 52919 [details]
Backtrace

Version:           unspecified (using KDE 4.5.2) 
OS:                Linux

konqueror crashes when viewing a directory containing Canon 7D CR2 raw images. Just moving the cursor above one of the file entries is enough to crash konqueror. It is independant of the view mode, be it icon detail or tree mode.

This worked before hundreths of time w/o any problem. One of the last updates from the openSUSE repos must have killed that. I even believe it's in the libtiff3, but I'm not sure, because libtiffs wasn't updated fir weeks.




Reproducible: Always
Comment 1 Frank Reininghaus 2010-10-27 22:55:43 UTC
Thanks for the bug report! Can you attach a file that can be used to reproduce the crash?

Pasting backtrace:

Thread 2 (Thread 0x7f37026c3710 (LWP 4532)):
[KCrash Handler]
#6  0x00007f3718f7496b in memcpy () from /lib64/libc.so.6
#7  0x00007f36fa3c6639 in (anonymous namespace)::strigi_tiffReadProc (handle=<value optimized out>, buf=0x7f36fc11c7a8, size=<value optimized out>) at /usr/include/bits/string3.h:52
#8  0x00007f37083ed7b1 in ?? () from /usr/lib64/libtiff.so.3
#9  0x00007f37083ee768 in ?? () from /usr/lib64/libtiff.so.3
#10 0x00007f37083ef8f6 in ?? () from /usr/lib64/libtiff.so.3
#11 0x00007f37083efe12 in ?? () from /usr/lib64/libtiff.so.3
#12 0x00007f37083d1348 in TIFFGetField () from /usr/lib64/libtiff.so.3
#13 0x00007f37083fab82 in TIFFScanlineSize () from /usr/lib64/libtiff.so.3
#14 0x00007f37083d3d31 in TIFFReadDirectory () from /usr/lib64/libtiff.so.3
#15 0x00007f37083f1bf0 in TIFFClientOpen () from /usr/lib64/libtiff.so.3
#16 0x00007f36fa3c6dc2 in TiffEndAnalyzer::analyze (this=0x7f36fc08bfb0, ar=..., in=0x7f36fc064cd0) at /usr/src/debug/kdegraphics-4.5.2/strigi-analyzer/tiff/tiffendanalyzer.cpp:201
#17 0x00007f37136ff332 in Strigi::StreamAnalyzerPrivate::analyze (this=0x1b, idx=..., input=0x7f36fc064cd0) at /usr/src/debug/strigi-0.7.2/src/streamanalyzer/streamanalyzer.cpp:421
#18 0x00007f3713ca7675 in KFileMetaInfoPrivate::init (this=<value optimized out>, stream=..., url=<value optimized out>, mtime=1287684310, w=<value optimized out>) at /usr/src/debug/kdelibs-4.5.2/kio/kio/kfilemetainfo.cpp:270
#19 0x00007f3713d34cc8 in KFileMetaInfo::KFileMetaInfo (this=0x7f37026c2d20, path=<value optimized out>, w=<value optimized out>) at /usr/src/debug/kdelibs-4.5.2/kio/kio/kfilemetainfo.cpp:299
#20 0x00007f3713d536ea in KLoadFileMetaDataThread::run (this=0x1896970) at /usr/src/debug/kdelibs-4.5.2/kio/kfile/kloadfilemetadatathread.cpp:130
#21 0x00007f371a4938be in QThreadPrivate::start (arg=0x1896970) at thread/qthread_unix.cpp:266
#22 0x00007f371a204a4f in start_thread () from /lib64/libpthread.so.0
#23 0x00007f3718fc582d in clone () from /lib64/libc.so.6
#24 0x0000000000000000 in ?? ()
Comment 2 Christoph Feck 2010-10-28 01:07:02 UTC
If you search for "TIFFRead" in bugzilla, you will get some other bug reports. Looks like a bug in libtiff which should be reported upstream (together with a file to reproduce).
Comment 3 Roman Fietze 2010-10-28 19:23:55 UTC
(In reply to comment #1)

> Thanks for the bug report! Can you attach a file that can be used to reproduce
> the crash?

Hmm, can I really attach files 30 MB in size? Don't think this makes sense, so I provided one here:

  http://www.fietze-home.de/digikam/20101019-163146.cr2

I think I found some detail information. The files that are landscape do not cause that problem, the files in portrait orientation do.
Comment 4 Dario Andres 2010-12-12 20:41:19 UTC
[Comment from a bug triager]
Merging with other strigi/tiff bug report: bug 250738.
Thanks for the information and the testcase

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