Anyone know how a stage causes Mugen to Not Respond indefinetly in 1.0?

[Gaulbetti]

I have nearly 3000 stages, and there is only one stage to my knowledge that holds my Mugen on the black screen between Vs screen and the match indefinitely. I have a couple graphic intensive stages that do briefly cause it to Not Respond but it eventually loads, but for one unknown stage in particular freezes it for good. I tried waiting it out, trust me. Is there a known coding error that specifically causes this to happen that could help me find this stage easier?

 

The last thing I know for sure, is that when using certain lifebars that eliminate the "fade in" Mugen does when everything loads after Vs Screen, character sounds that play Frame 1 can be heard before Mugen stops responding. Even Mugen.log hasn't helped me catch this stage with that. Thanks in advance, trying to dig through each stage I have but it's tedious.

[jrm1007 - Rin]

Some Stages are created in an incredibly odd manner, that being, an incredibly small square being tiled to infinity. This will cause MUGEN to generate millions of these tiny squares in order to fill the screen. This causes major FPS issues and can be one manner of causing the Engine to cease up.

 

A Similar situation can occur if an Animation is set to "Tile" but does not have a "Tilespacing" value, causing the same animation to tile infinitely in the same spot, rather than spreading out as intended, this will cause millions of animations to tile in the same spot.

 

There can also be faulty coding for the BG Elements as well.

With Stages it's much easier to narrow down what could be causing the freeze, If you find out the stage that's causing issues, open it up and look for Sprite sizes and what not.

There's also a possibility of the SFF being corrupted.