The browser version seems to open it fine every time for me. I can reproduce it taking forever with the NW.js version though. It seems to just fall idle and stop doing any further work. That's really weird and I don't know why that would happen - my best guess is there's another problem with the new Closure Compiler minifier we switched to recently. It may be that the next update of that fixes the issue since they fixed a bug that was affecting our code recently, so I'll try updating to that when it's out as a first step.

It still reproduces for me after updating Closure Compiler, so I don't think it's to do with that. I've made some adjustments to the loading scheduling for the next release which seems to have solved it for me, but it's quite hard to tell since it's relatively unpredictable. Marking to check when the next release is out to verify.

@aiaicaptain - r215 is now out, can you verify if it's working with that release?

No, the problem persists for me.

I could previously reproduce this before, but now with r215 it seems to reliably open the folder project. I tried 5 times with the browser and 5 times with the desktop build (NW.js 0.48.1) and it worked fine every time. Are you sure you were trying with r215?

Hmmm, the project I attached to this issue really does open, but my personal huge project does not still. The only difference in terms of specs between the two are that my project has around 4k events +, along with many sprites. I even tried deleting a bunch of sprite objects to drastically lower the sprite count (this actually worked before), but now it won't open with even a low sprite count. Is there a chance that now it hangs up because of high event count?

No, skip that, I deleted ALL events in my project and still it didn't run. I can't get it to open under 215 at all anymore (desktop, folder based) at all. i can still open it (and still every 5th attempt) from the browser version.

I can upload a severely trimmed down version of my project, if you are willing to try and open it it'd be awesome.

I think if the size of the project is the problem, it's best to address this with the actual original project. Could you send it to me at ashley@scirra.com if you don't want to share it publicly?

Also can you confirm what version of NW.js you are using? 0.48.1 is the latest, and some old versions are probably buggy, so you should make sure you're up-to-date.

Project received by email but seems to work fine for me here, successfully opened as a folder project 10 times in a row with r215.

Unable to further reproduce, so closing issue.