The save state increases over time when saving and loading. It seems to happen when creating objects that are then destroyed "on collision".
Attach a Capx
Description of Capx
The capx creates a sprite every tick that immediatly gets destroyed on collision. Then every second the state is saved then loaded.
Steps to Reproduce Bug
Basically exactly like the capx, but...
- Every tick create a sprite so it overlaps a second object.
- Using the "on collision" condition check for a collison between the sprite and object and then destroy the sprite.
- Periodically save then load the game state.
After a few saves and loads of the state, the save state gets bigger and bigger. Looking at the JSON string the section after "collmemory" gets longer and longer.
That the savestate would remain the same size
- Chrome: untested
- FireFox: YES
- Internet Explorer: untested
Operating System and Service Pack
Windows Vista sp2
Construct 2 Version ID
Further discussion on the bug found here: