Summary: | Nepokuk server intermitently crashing while indexing. | ||
---|---|---|---|
Product: | [Unmaintained] nepomuk | Reporter: | jbrsubscribe |
Component: | general | Assignee: | Sebastian Trueg <sebastian> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | agente2012, david-sarah, evengard, j_macharia, mail, michael.murphy, nico.kruber, public, tonesenna, trueg, veresp |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 4.7.1 | |
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
DrKonki crashlog DrKonqi crashlog valgrind logfile valgrind shell output New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi |
Description
jbrsubscribe
2010-08-18 14:38:39 UTC
Created attachment 50836 [details]
New crash information added by DrKonqi
nepomukservicestub (0.2) on KDE Platform 4.5.00 (KDE 4.5.0) using Qt 4.6.3
- What I was doing when the application crashed:
letting strigi index my files using virtuoso backend (soprano-virtuoso.db ~4.2GB - but I'm working on an even larger DB on another computer and haven't seen a crash so far...)
-- Backtrace (Reduced):
#11 0x00007f3e0a936dac in QString::free (d=0xff4c30) at tools/qstring.cpp:1108
#12 0x00007f3e0a937322 in QString::operator= (this=0x6c1258, other=@0x1358090) at tools/qstring.cpp:1282
#13 0x00007f3dfb140974 in Nepomuk::IndexScheduler::updateDir (this=0x6c1200, dir=..., analyzer=0x7f3dfa276e10, flags=...)
at /usr/src/debug/kdebase-runtime-4.5.0/nepomuk/services/strigi/indexscheduler.cpp:337
#14 0x00007f3dfb141325 in Nepomuk::IndexScheduler::updateDir (this=0x6c1200, dir=<value optimized out>, analyzer=0x7f3dfa276e10, flags=...)
at /usr/src/debug/kdebase-runtime-4.5.0/nepomuk/services/strigi/indexscheduler.cpp:422
#15 0x00007f3dfb141325 in Nepomuk::IndexScheduler::updateDir (this=0x6c1200, dir=<value optimized out>, analyzer=0x7f3dfa276e10, flags=...)
at /usr/src/debug/kdebase-runtime-4.5.0/nepomuk/services/strigi/indexscheduler.cpp:422
*** Bug 248227 has been marked as a duplicate of this bug. *** *** Bug 248797 has been marked as a duplicate of this bug. *** Created attachment 51483 [details]
DrKonki crashlog
The crash occurred after have :
- installed latest kernel patch for oS 11.3
- upgraded dbus to version 1.4
@Alvise: can you reproduce this crash? And if so would you be willing to run it through valgrind? You could do that my disabling Nepomuk in the systemsettings, then start "valgrind -v --log-file=XYZ nepomukservicestub nepomukstorage", and then once you got a ton of output re-enable Nepomuk in the systemsettings. Created attachment 51704 [details]
DrKonqi crashlog
Sure.
Here is at last a crash while I was running with valgrind
Created attachment 51705 [details]
valgrind logfile
Created attachment 51706 [details]
valgrind shell output
Created attachment 53034 [details]
New crash information added by DrKonqi
nepomukservicestub (0.2) on KDE Platform 4.5.1 (KDE 4.5.1) using Qt 4.7.0
Whenever I ignite the equipment the application does crash
-- Backtrace (Reduced):
#14 0x00a540ad in qFree (ptr=0x9b057f8) at global/qmalloc.cpp:60
#15 0x00aa50b0 in QString::free (d=0x0) at tools/qstring.cpp:1151
#16 0x00aa550e in QString::operator= (this=0x972682c, other=...) at tools/qstring.cpp:1325
#17 0x021c7b0e in Nepomuk::IndexScheduler::updateDir (this=0x9726800, dir=..., analyzer=0xb54532fc, flags=...) at ../../../../nepomuk/services/strigi/indexscheduler.cpp:337
#18 0x021c857a in Nepomuk::IndexScheduler::updateDir (this=0x9726800, dir=..., analyzer=0xb54532fc, flags=) at ../../../../nepomuk/services/strigi/indexscheduler.cpp:421
Created attachment 53159 [details]
New crash information added by DrKonqi
nepomukservicestub (0.2) on KDE Platform 4.5.3 (KDE 4.5.3) using Qt 4.7.0
I was just using my KDE desktop normally, when the message of the crash appeared
-- Backtrace (Reduced):
#11 0x00007f4d4c9ee2ec in QString::free(QString::Data*) () from /usr/lib/libQtCore.so.4
#12 0x00007f4d4c9ee862 in QString::operator=(QString const&) () from /usr/lib/libQtCore.so.4
#13 0x00007f4d3d291cc4 in Nepomuk::IndexScheduler::updateDir(QString const&, Strigi::StreamAnalyzer*, QFlags<Nepomuk::IndexScheduler::UpdateDirFlag>) () from /usr/lib/kde4/nepomukstrigiservice.so
#14 0x00007f4d3d292675 in Nepomuk::IndexScheduler::updateDir(QString const&, Strigi::StreamAnalyzer*, QFlags<Nepomuk::IndexScheduler::UpdateDirFlag>) () from /usr/lib/kde4/nepomukstrigiservice.so
#15 0x00007f4d3d292675 in Nepomuk::IndexScheduler::updateDir(QString const&, Strigi::StreamAnalyzer*, QFlags<Nepomuk::IndexScheduler::UpdateDirFlag>) () from /usr/lib/kde4/nepomukstrigiservice.so
Is the bug abbandoned? The crashes persist on KDE 4.5.5 Evengard, if you can reproduce it, please add a valgrind log. in 4.6 it is reproduced VERY rarely, so for now I can't reproduce it with valgrind. *** Bug 279503 has been marked as a duplicate of this bug. *** *** Bug 241180 has been marked as a duplicate of this bug. *** *** Bug 270844 has been marked as a duplicate of this bug. *** Fixed in 4.7.1 *** Bug 285618 has been marked as a duplicate of this bug. *** Created attachment 66509 [details]
New crash information added by DrKonqi
nepomukservicestub (0.2) on KDE Platform 4.6.5 (4.6.5) using Qt 4.7.2
- Unusual behavior I noticed: Seg faults repeatedly when matlab & eclipse are debugging.
-- Backtrace (Reduced):
#6 0x00007f8d49d06c07 in malloc_consolidate (av=0x7f8d4a01e1c0) at malloc.c:5161
#7 0x00007f8d49d08472 in _int_malloc (av=0x7f8d4a01e1c0, bytes=1048) at malloc.c:4373
#8 0x00007f8d49d0b31e in __libc_malloc (bytes=1048) at malloc.c:3660
[...]
#11 0x00007f8d4c0cc30f in QHashData::rehash (this=0x234a3d0, hint=<value optimized out>) at tools/qhash.cpp:364
#12 0x00007f8d4b0184b7 in reserve (this=0x7fff50f261f0) at /usr/include/qt4/QtCore/qhash.h:847
|