Layout memory cleanup

Does anyone know what the memory cleanup is after you Goto a new Layout? I can't find any mention of this in the documentation. If I created a bunch of objects and don't destroy them it seems like they are cleaned up for you? When I go back to that layout they are gone and the level restarts. However, eventually as I play, the game's FPS slows down, especially when I add lots and lots of objects and it seems to happen progressively.

Since then I've put all my created objects in a family and I just destroy them all right before I leave the layout and it seems to have done the trick.. I haven't seen any slow down..

Can anyone confirm what happens memory-wise when switching layouts?

no one knows?

I don't encounter that problem you describe, can play for hours and no slow downs.

Do you run with WebGL mode enabled?

— yes, webgl and the latest Chrome

Normally C2 does a destroy on all non global object after each layout (however if you spawn other object on destroyed, they'll not be erased)

However it could have changed slightly from the last time I worried about this, so maybe there is a problem indeed

Aphrodite, I'm pretty sure it doesn't. I was able to recreate the performance hit when spawning many many objects between layouts. It didn't happen right away, but then all of a sudden my fps would go down to 20 when it's normally at 60 (and I have a very fast computer). It felt like a cleanup issue to me, since destroying the Families at the end seems to do the trick. I was just looking for the official word as I couldn't the answer anywhere.

Sounds like it might be a bug, can you provide a simple .capx that reproduces the issue?

unfortunately the game I am working on is over 350 events and quite large. It very well could be a bug. I hope not.

Arima do you know of any doc that might explain what happens to "System->Create Objects" after a Layout is left? I figure globals and objects with the Persist behavior remain intact.