Problem with ksycoca on windows
thiago at kde.org
Fri Feb 15 13:17:44 GMT 2008
On Friday 15 February 2008 13:50:45 David Faure wrote:
> Assuming kded is always running, we wouldn't leak resources if an
> application merely using the shared-memory-for-ksycoca (in a readonly way)
> crashes, right?
But I don't know how this would work.
If kded is allowed to update the ksycoca shared memory, then we need a global
locking mechanism (QSystemSemaphore). If it's read-only by kded too, then
when should it dispose of old shared segments?
The good thing about a file-backed shared memory (i.e., mmap) is that it goes
away when all applications unmap. And if the file was deleted, it is reaped
at that time too.
It's too bad that Windows doesn't support Delete-on-close semantics.
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 189 bytes
Desc: This is a digitally signed message part.
More information about the kde-core-devel