Talk:Soda Swamp (Episode 66)/@comment-26235098-20150529115529/@comment-26235098-20150531115001

I actually suspect they may have some concurrency errors. Some of the glitches that happen (since forever) and some odd timing symptoms (eg bomb goes off while odus falls, timing varies) look like they  are multithreaded and not strictly synchronized. The single-stripe-formed-but-not-detonated during Crush also screams "race condition" to me. Hadn't observed any such thing when returning to the map, but have seen occasional odd behavior there in past. Concurrency issues are typically not seen by all users, and vary slightly across users, because they will change with procspeed, chipset, memory/memspeed, resource use, system efficiency... and on. These are extremely, extremely difficult bugs to find.

Personally, I'd want the product rolled back to previous release, since the massive problems were not seen before this episode. Then, comb through the changes made inhouse, with stepwise regression testing. But people have played the new stuff now and will be pissed if they lose their scores. I could care less. I'd replay it... better than all the lives I'm losing in DW right now.

The other thing is, Flash could be the cause of the issues, in which case, Adobe may be at fault, not King. The Flash runtime/plugin DOES seem to have problems... like a major memory leak for one thing. I see it with other things, not just this game.