Summary: | Nepomuk crashed when adding new folders to be indexed. | ||
---|---|---|---|
Product: | [Unmaintained] nepomuk | Reporter: | Luis Silva <lacsilva> |
Component: | filewatch | Assignee: | Nepomuk Bugs Coordination <nepomuk-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | bladud, me, nepomuk-bugs |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Patch |
Description
Luis Silva
2012-11-29 17:03:37 UTC
Are you really running 4.9.3? From the backtrace it looks like the assert was one only added for 4.10 I should have said this before. I am using binary packages from 4.9.3 from kubuntu but I compiled the nepomuk stack (soprano, nepomuk-core) from master. Ok, thanks. You can 'fix' this by compiling the packages in release build: pass -DCMAKE_BUILD_TYPE=Release to cmake (this should also make nepomuk much faster). Aside from that, it is a little bit strange the assert triggered, and I'd like to understand why. (You aren't trying to index '/', are you? There are other reasons that won't work too well. ) The only other possibility I can think of offhand is that EventQueueOverflow is happening. Were you moving a lot of files around at the same time as adding the watches? Created attachment 75741 [details]
Patch
Could you try the attached patch? If the bug triggers again, it should give us some more idea why.
Thanks
> (You aren't trying to index '/', are you? There are other reasons that won't work too well. )
No, I am and was not trying to index /
I will be trying this patch in the next few days.
Ok! I tried the patch and I seem to not have had this crash anymore. However, I cannot reproduce the crash without the patch either. It seems to have been a one-time thing. Answering Comment #3, no, I was not indexing '/' or moving files at the time. However, I was adding a hidden folder to the index which was implicitly excluded by the default eclusion rules. Please reopen this bug if it happens again. For now, I'm marking it as FIXED. |