> > Something is causing memory to keep increasing. The memory goes up and up. If objects were being flushed than memory would drop. Something is still running in previous layouts. I re-use Sprites from previous layouts.
> > Do Sprites that are used later persist in memory from previous layouts?
> In my past experiments. There are some cases.
> If the sprites from your old layout is present in your new layout then it won't be flushed but if it isn't present in the next layout then it will be flushed.
The Sprites from the old layout are present in the new layout.
Thank you for this information. That could explain what is going on.
Will doing at End of Layout > Destroy A destroy the sprite and flush it from memory?
On End of Layout > Destroy A
A B C and are on the current layout. Will that function destroy A B and C, even if they are present on the next layout?
I think you misunderstood something Phoenixbowman .
The images of the sprite are the only thing stored in the memory not the sprites or objects nor instances. The instances you are talking about (The Objects on the layout, THE number of sprites) are codes that are generated by the things you put in the layout or you created using the eventsheet.
IE: 100 instances of 1 sprite of 32x32 image
(100 instances are code during layout and not persisted on next layout in other words they are only available in that layout and is cpu based not memory.)
(1 sprite of 32x32 image is stored in the memory)
1 image of 32x32 image or frame is stored in the memory and the cpu is used to make them 100 instances and do movements.