[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Nepomuk: re-checking the strigi index constantly



Am Mittwoch 31 März 2010 schrieb Michael Schuerig:
> On Wednesday 31 March 2010, Martin Steigerwald wrote:
> > Am Dienstag 30 März 2010 schrieb Michael Schuerig:
> > > On Sunday 28 March 2010, Michael Schuerig wrote:
> > > > Apparently, a new
> > > > /usr/bin/nepomukservicestub nepomukstrigiservice
> > > > is started every 8 or 9 minutes. from ~/.xsession-errors I can't
> > > > see anything that indicates that these processes are crashing.
> > > 
> > > Well, strace and gdb know better. Indexing is interrupted, when an
> > > assert statement fails and causes a SIGABRT
> > > 
> > > # strigi-0.7.1/src/streamanalyzer/lineeventanalyzer.cpp:180
> > > void
> > > LineEventAnalyzer::handleUtf8Data(const char* data, uint32_t
> > > length) {
> > > 
> > >     assert(!(sawCarriageReturn && missingBytes > 0));
> > 
> > That sounds simular to my bug report (see mail "nepomuk strigi
> > service crashed too often" in this list):
> > 
> > https://bugs.kde.org/232395
> 
> Similar, but probably not the exact same. In my case, there are no
> indications in ~/.xsession-errors that anything went wrong. I've seen
> messages of the "crashed to[o] often" kind for *other* problems, but
> not for this specific one.
> 
> /usr/bin/nepomukservicestub and nepomukservices aren't very helpful as
> the process name, have you tried looking at the complete commandline?
> In top it's toggled by pressing 'c'.
> 
> AFAIUI, Soprano is part of the storage backend used by Nepomuk, whereas
> Strigi belongs to the frontend retrieving the (meta)data. Your problem
> appears to occurs, when Nepomuk tries to store data in Soprano. Then
> the question is, where that data comes from and why it is malformed.

Yes, on the second look the issues sounded a bit different. Well, I put 
some cross links in there, may the developers decide ;). I also added your 
crash handling suggestions to my bug report

https://bugs.kde.org/show_bug.cgi?id=232398

as they are quite similar to what I suggested. I suggest you use your bug 
report for informations on the crashes you encounter and let us share bug 
#232398 for the crash handling stuff in Nepomuk.

-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: