I just noticed that the Editor will freeze and begin eating RAM when you do the following:
Right click the attached “2DCharacter_IdleAnimAtlas” image and go to Sprite Actions > Extract Sprites.
Change Sprite Extract Mode to “Grid”.
Reset the Cell Width back to 0, and change Cell Height to 256. (Naturally, you wouldn’t use a 0 setting in real life, but this is to demonstrate how easily one can accidentally freeze the Editor and begin eating RAM. You will need to kill the process manually in Windows Task Manager.)
Thanks very much for your time in looking into this!
Following your repro steps, I was not able to reproduce the issue; Instead, while taxing my system pretty hard, the test resulted in producing an inordinate amount of sprites after about 6 minutes of processing:
Note the arrow on the far right on the scroll bar which signifies a total of six or seven times the total amount of sprites shown here. Naturally, you would not set the cell width to Zero but even if you do, as shown here, if your system can handle it, it will not fail and so it is technically not a bug.
If you feel this does not accurately represent the issue you are reporting, let me know and we’ll look into it further.
Thanks very much, , for looking into that. Well, you must have a whopping system then, or else I didn’t wait long enough on my six-core i7 with 32 GB of RAM. Once the Editor completely ceased responding to input, I assumed something was wrong. So yes, perhaps it’s technically not a bug, but it’s definitely “bug-like behavior” that’s too easy to trigger, especially considering I didn’t even click “Extract Sprites”. I just clicked the “Reset to default” arrow which set it to zero causing the Editor to freeze and begin eating RAM.
Thank you again for checking it out. That’s greatly appreciated.