Summary: | Nepomuk crashes while modifying a large PDF file (or another situation related to files changing) [free, ~QString, QFSFileEngine::fileFlags, QFileInfoPrivate::getFileFlags, ..., Nepomuk::IndexScheduler::analyzeDir] | ||
---|---|---|---|
Product: | [Unmaintained] nepomuk | Reporter: | Ulrich Lichtenegger <ulilicht> |
Component: | general | Assignee: | Sebastian Trueg <sebastian> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | andresbajotierra, ismail, me, trueg, ubuntudenver, ulilicht |
Priority: | NOR | ||
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Ulrich Lichtenegger
2011-07-09 13:35:29 UTC
[Comment from a bug triager] From bug 279016 (KDE SC 4.6.5): -- Information about the crash: Neopmuk crashes while scanning media. This continues to happen after applying KDE 4.6.5 updates. Bug 276903 has a similar backtrace. Additionaly, the crashes at bug 275169 could be related. (similar backtrace and situation) *** Bug 279016 has been marked as a duplicate of this bug. *** Created attachment 62903 [details]
New crash information added by DrKonqi
nepomukservicestub (0.2) on KDE Platform 4.7.00 (4.7.0) using Qt 4.7.2
- What I was doing when the application crashed:
i was downloading a large encrypted file via chromium
-- Backtrace (Reduced):
#9 0x00007fc134f4cbb6 in malloc_printerr (action=3, str=0x7fc13502b980 "malloc(): memory corruption (fast)", ptr=<value optimized out>) at malloc.c:6283
#10 0x00007fc134f4fe78 in _int_malloc (av=0x7fc120000020, bytes=<value optimized out>) at malloc.c:4308
#11 0x00007fc134f5231e in __libc_malloc (bytes=96) at malloc.c:3660
#12 0x00007fc137329415 in QString::QString (this=0x7fff954082c0, size=32) at tools/qstring.cpp:1099
#13 0x00007fc137402078 in QUtf8::convertToUnicode (chars=<value optimized out>, len=31, state=0x0) at codecs/qutfcodec.cpp:183
*** This bug has been marked as a duplicate of bug 282124 *** |