It's a known issue. From my limited understanding on why this happens I'd wagger it's got to do with how they instance the is created and what happens if, for some reason, they get some type of network issue whilst loading up the character info. I'm sure they'll get around to fixing it, as it's a very annoying thing and, IMO, it shouldn't be a HUGE issue and is probably related to the variable initialization order, and the generally asynchronous by definition network enviroment.
TLDR : It will be fixed soonish.