[Nepomuk] High mutex contention in Nepomuk2::Resource

Simeon Bird bladud at gmail.com
Fri Mar 8 16:10:50 UTC 2013


Note that I detected an error in the use of the "modification mutex" within

> Resource. I had used it only for "writes" to variables, but obviously the
>> reads must be mutex-protected too. Now that I understand the C++11 memory
>> model, it's a lot clearer :)
>> I'll rename the mutex then, it's not a "modification mutex", it's a mutex
>> for
>> the resource member variables.
>>
>
> Uhm. Okay.
>
>
Does the extra locking fix
https://bugs.kde.org/show_bug.cgi?id=305024which is some sort of
memory corruption in the client-side resource
watcher? It seems to be threading related, since it is intermittent...

Simeon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/nepomuk/attachments/20130308/91047733/attachment.html>


More information about the Nepomuk mailing list