Re: For "known issues": Too much memory
I apologize for not commenting on this workaround earlier. I did see several reports of this problem, as well as the suggested workaround, and know that one of our SWQA engineers was able to confirm it helps on one of his systems. However, I have not had a chance to determine what the problem is, exactly, and don't feel comfortable documenting the workaround speculatively. We have a bug tracking this issue internally, however, and hope to get to the bottom of it, eventually.