Bug 273550 - Metadatareader crashes hovering over file
Summary: Metadatareader crashes hovering over file
Status: RESOLVED WORKSFORME
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-18 11:05 UTC by simon
Modified: 2011-05-18 23:27 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description simon 2011-05-18 11:05:22 UTC
Application: kfilemetadatareader ()
KDE Platform Version: 4.6.41 (4.7 >= 20110106) (Compiled from sources)
Qt Version: 4.7.2
Operating System: Linux 2.6.38.6-zen-01981-ga3c54ec x86_64
Distribution (Platform): Gentoo Packages

-- Information about the crash:
- What I was doing when the application crashed:

just staying abit over a file in dolphin makes the metadata reader crash , hope the backtrace helps

The crash can be reproduced some of the time.

-- Backtrace:
Application:  (kfilemetadatareader), signal: Aborted
[KCrash Handler]
#6  0x00007f1d232ba445 in raise () from /lib/libc.so.6
#7  0x00007f1d232bb941 in abort () from /lib/libc.so.6
#8  0x00007f1d232f6a3f in __libc_message () from /lib/libc.so.6
#9  0x00007f1d232fc0f8 in malloc_printerr () from /lib/libc.so.6
#10 0x00007f1d2368c359 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string() () from /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.5/libstdc++.so.6
#11 0x00007f1d232bcfd5 in __run_exit_handlers () from /lib/libc.so.6
#12 0x00007f1d232bd025 in exit () from /lib/libc.so.6
#13 0x00007f1d232a6bad in __libc_start_main () from /lib/libc.so.6
#14 0x0000000000403079 in _start ()

Possible duplicates by query: bug 273447, bug 273144, bug 273136, bug 273119, bug 273042.

Reported using DrKonqi
Comment 1 Christoph Feck 2011-05-18 14:46:42 UTC
Can you compile strigi with full debug symbols available and run it through valgrind? Which strigi version are you using?
Comment 2 simon 2011-05-18 23:27:29 UTC
ok it seems my ffmpeg was too new , i downgraded and the crash is gone!