I agree, FIX FOR THE CRASHES NEEDS TO BE A TOP PRIORITY. This problem has been there for way too long. Pull people from other projects for a while if needed, but the game needs to be fixed before adding new content.

I don't fully agree that it is just fixing small things here and there or optimizing the graphical content. There are bigger issues in there as well. When looking at the memory allocation and release of the lotroclient it's clear that there are some real issues. When you move between the areas in game the client doesn't properly release the memory from previous areas, but keeps accumulating the memory until it crashes. It is also very obvious that when application is getting closer the memory limit you get lots of stutter and glitches in frame rate. Game is silk smooth when you load it, but more you play (and more memory the app has accumulated) more stutter you get when app is doing the memory allocation/release on the fly and obviously quite inefficiently or slowly. Again a clear indication of problematic memory handling. I wouldn't be surprised if lag and rubberbanding has some connection to this as well since client-server communication is probably having similar "stutter" when app is closer to memory limit and app is spending a lot of time on memory handling instead of communicating with server.

It shouldn't be too hard to debug the code to see how the memory is allocated/released (to remove stutter) and to identify why release isn't done properly (to avoid crashes).

In game I hate going to MT and other new areas. I also hate to participate in group content since I don't want to crash while being part of the group in instance. It is certainly not worth the VIP subscription which I cancelled already.