I was curious so I figured I'd test this out. Feels a lot like optimization issues in the 1.0 release with the EX stage.
On my main machine (Ryzen 3700X, GTX 970, 32GB of RAM, game and system drive are located on an NVME SSD) I have not had this issue and have not been able to replicate it, so I figured I'd try my lower-end laptop (i5 8300H, 8 GB RAM, GTX 1050, HDD only, to my shame), where I was able to replicate it pretty easily..
Running it with the onboard graphics, it would consistently crash with a memory access violation error (0xC0000005) on loading the stage, with the faulting module being libcocos2d.dll. However, running it with the GTX 1050, it would instead just not load certain assets. Sifting through event viewer logs, I found that NVidia had a few warning messages that it was out of memory and unexpected behavior might occur.
After restarting the machine it worked "okay" but slowly, though I think this is because Windows Defender was absolutely thrashing my HDD scanning the game files. Seems to point to the game trying to get more memory that just isn't available to it until on a fresh restart.
It's worth noting that if it is memory issues, then restarting and running it with fewer things open really might fix it (for a while). However, if you're using Windows 10 you'll want to make sure you're specifically restarting instead of using shut down and manually powering it on because W10's fast startup behavior will likely not fix this issue (see
You must be registered to see the links
for more details).