[Amarok] b18a028: Use shared memory for collection scanner to rememb

Jeff Mitchell mitchell at kde.org
Sat Nov 6 14:03:34 CET 2010


On 11/06/2010 05:38 AM, Maximilian Kossick wrote:
> One of the reasons for collection scanner as a separate executable was
> to prevent a crash in collectionscanner from bringing down Amarok as
> well. As both processes only communicated with each other via files or
> stdout/stdin, this was relatively safe. Is it ensured that a
> corrpution of the shared memory data does not crash both processes?

This is especially important as TagLib has a history of being quite
crashy on corrupted files (which are quite common). (The old ScanManager
tried to skip such files if the scanner was crashing on a particular
file (with mixed success) by restarting the scanner.)

--Jeff

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
Url : http://mail.kde.org/pipermail/amarok-devel/attachments/20101106/fb417268/attachment.sig 


More information about the Amarok-devel mailing list