I had a notification script set up to load an emergency playlist when the playlist ran empty (per sample script PlaylistEmpty.mls) but it was pointing to the wrong drive so when the playlist ran empty mAirList tried (and failed) to open the emergency playlist (3435 times according to the system log!) and then hung. Would it be worth limiting the number of tries to a sensible amount - which presumably will prevent the whole system hanging?
Additional info: If PlaylistEmpty.mls references a playlist file which does not exist then mAirList just carries on. The problem described above occurs when the playlist referenced in the PlaylistEmpty.mls script if present but contains files which cannot be loaded.
Same thing happens in the demo version of V4.0.1 b1205