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
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Amarok-devel mailing list Amarok-devel@kde.org https://mail.kde.org/mailman/listinfo/amarok-devel
