I am very sorry for the long, long overdue response on this issue. I wanted to make sure I had all of my information correct before responding again.
When I last spoke to you guys, I said that QA was "actively researching" this issue. Since then, QA has worked directly with the programmers to reproduce this issue internally on both Nvidia and AMD machines.
As Graysdir has mentioned several times, this is not the same as the "loading assets" issue. We were able to reproduce this issue after verifying that 100% of our assets have loaded.
A bug has been logged and assigned to the programming team. I don't have any more information to give you guys other than that.
I know it can seem like Blizzard has been ignoring this issue, but we truly haven't. I honestly wanted to wait to respond until I could tell you exactly what was happening. With a specific bug for this issue logged into the database, we are one step closer to fixing this issue for you guys.