The only issue I ever had with fling was on my old XP box. When I started using it for clientraw uploads, it would build non-paged memory until the system ran out, and basically crashed. This would happen every 4 days based on the clientraw timer I used. I changed a bunch of file create frequencies, and moved clientraw upload to WD, and got the condition under control. the NP memory still would build but at the rate, it would take 40 or 50 days to build too high. This behaviour did not seem to recur on my new Win7 box. Of course I dont think it happened on my original XP box either, but I was just loading basic VWS files, and a 60 second update wflash file back then.
I dont know if there is a startwatch feature that might be able to help, might be.
But have you looked at resources, etc being used by Fling and Salsa as this even approaches? NP memory is not in taskman list by default, you have to add it. However even if I could monitor NP for my old issue, closing fling and restarting would not actually free the memory, it did not show in use on taskman fling process, but was not actually free up system wide. A reboot was only way to flush.
Andrew