Trust me, we are well aware that parts of our code needs an overhaul - we are in the process of rewriting those parts right now. Devs have been killing a lot of crash bugs these last couple of weeks, but it's a big change to core functionality and we want to make sure we're not introducing any new bugs, so that's why it's taking some time.
As I've said before though, the crashes described in this thread are not all the same and that's why there's not one universal solution to all of them.
If you, for example, had your playlists sorted in folders, and they have somehow magically been reordered or are just acting weird in general, in turn causing the client to crash, then it's an old backend issue (that has been fixed) and David or someone else from customer support can help you sort it out.
If you're having the "playlist update" problem seen above, then it's a timing/threading issue in the client. I've only managed to reproduce that issue once, on the subway and with bad connection, and in my case going offline for a minute or two helped. I know it's worked for some others as well. It's not a good solution, but might help some of you until we have the new client out.
@alanmc - CS can help you get your playlists back, if you want.
Last but not least; I know you guys are frustrated, understandably so, but please don't take it out on those who are actually trying to help you.
That is all. Sorry to the tl;dr crowd.
