[Bug 251795] Nepomuk related crash on startup (4.6) [QMutex::lock, QMutexLocker, Soprano::Client::SocketHandler::~SocketHandler, ..., Nepomuk::MainModel::init]

[Sebastian Trueg]

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





--- Comment #31 from Sebastian Trueg <trueg kde org>  2011-09-23 09:13:56 ---
(In reply to comment #28)
> On Thursday 22 Sep 2011 13:45:48 Sebastian Trueg wrote:
> > https://bugs.kde.org/show_bug.cgi?id=251795
> > 
> > 
> > 
> > 
> > 
> > --- Comment #27 from Sebastian Trueg <trueg kde org>  2011-09-22 13:45:48
> > --- (In reply to comment #26)
> > 
> > > I can (sort of)reproduce this bug with Project Neon ( which is currently
> > > using kdelibs master , and pretty much everything else from master as
> > > well ). Currently as soon as i start up my session , nepomukindexer
> > > starts hogging all my CPU's ( note this is a 8 core machine ) and then
> > > i have to kill the indexer manually via a SIGTERM to bring everything
> > > back to normal, giving me a backtrace similar to the one attached ( i
> > > reported it as a bug which was marked as a duplicate of this one ).
> > 
> > not related to this bug: can you provide the file that makes nepomukindexer
> > go wild?
> 
> I noticed (using the openSuse snapshots of -- I presume -- master) that what 
> happens is this: some files are apparently slow to index (I must still have 
> some of them on my disk, but mostly PDFs generated with inkscape: no text, 
> mostly drawings) Then, when the indexer gets stuck, it launches another. Now 
> if you have a bunch of these files, you may end up with 20 indexers running. 
> Eventually, if you wait long enough, they'll complete their tasks and things 
> will go back to normal. But in the meantime, the system gets hammered.
> 
> This may or may not be related.

This should have been fixed already here:
https://bugs.kde.org/show_bug.cgi?id=281779. Still it would be very helpful to
get such a pdf in order to improve the indexing speed.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.