Summary: | Storage Crashes when Virtuoso Crashes | ||
---|---|---|---|
Product: | [Unmaintained] nepomuk | Reporter: | Derek Frazier <ddfrazier82> |
Component: | storage | Assignee: | Sebastian Trueg <trueg> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | me, olevanosoldier |
Priority: | NOR | ||
Version: | 4.7 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/nepomuk-core/d93cb74cb99936ed1edd4a10f6d6b05fa6678c7c | Version Fixed In: | 4.10.2 |
Sentry Crash Report: |
Description
Derek Frazier
2012-02-25 19:58:49 UTC
*** Bug 292356 has been marked as a duplicate of this bug. *** It seems that one of Soprano::FilterModels does not have a parent, and is asserting cause of that. That is weird cause all the models always have parents, and their parents never ever change. I'm not sure what to do of this bug report. Confirmed. Crash virtuoso when some operations are going on in the storage service. The main repository's parent will be set as 0, and then reset to the new virtuoso model. In the middle the other threads can access it and they assert cause the parent of the model = 0. This can probably be fixed with a mutex. I'm not sure exactly how to go about it. Git commit d93cb74cb99936ed1edd4a10f6d6b05fa6678c7c by Vishesh Handa. Committed on 11/03/2013 at 19:45. Pushed by vhanda into branch 'KDE/4.10'. Repository: Never set the parent to 0 Use a dummy model instead. Setting the parent to 0 can cause a crash when some other threads are using the model. FIXED-IN: 4.10.2 M +3 -1 services/storage/repository.cpp M +3 -0 services/storage/repository.h http://commits.kde.org/nepomuk-core/d93cb74cb99936ed1edd4a10f6d6b05fa6678c7c |