Construct just saved a 91gb file

I was running construct, and I had a game I'm working on open, in my settings I have made it save a backup every minute.

I left it open and went to do something else. When I came to save a file on my hard disk it was completely full, strange, i thought, since i had around 100gb left last time i checked. I then realised what it was:

<img src="http://www.quotecats.com/what/lolstruct.PNG">

<img src="http://www.quotecats.com/what/lolstruct2.PNG">

pretty odd seeing as before that the size of the file was around 800kb

when i went back into construct it crashed horribly, presumably after it ran out of space to save. It sapped every remaining byte of my hard disk.

<img src="http://www.quotecats.com/what/lolstruct3.PNG">

this has to be the funniest bug i've ever seen, and fairly serious aswell. plz fix

Dont tell me the memory exploit is still at loose...

HAHAHAHAHA!!! THAT was funny! Well, this sure is a high priority bug!

Hopefully its just a bug with the "save a backup every minute" stuff

Its weird though because I've had that setting on for ages and it's never done anything like this. If i didnt have that setting on construct would be completely unusable (with crashes etc)

It's obviously rare, but if it has happened once it can happen again

Whilst it's amusing there's obviously a save problem (an infinite loop) going on..

Do you have any ideas what could've caused it or if you'd done anything (made a family, created an object, etc) just before it?

Thanks

nope, in fact i think i did absolutly nothing other than open the file, then go away and do something else, i can upload the latest backup before that if you want

You're using the 0.96.2 version yes?

You're using the 0.96.2 version yes?

yes

It must be related to auto-saving because I don't use that feature and have never had a size issue in any version.

eh.. since only one person has had this issue it could be related to anything.

I'm not sure if the upload forum will allow to upload that 91gb file or not.

It must be related to auto-saving because I don't use that feature and have never had a size issue in any version.

I tried that its not the auto-saving.

> It must be related to auto-saving because I don't use that feature and have never had a size issue in any version.

>

I tried that its not the auto-saving.

What I meant was, that when it is enabled, it allows a memory leak under certain conditions.

Whatever the actual cause may be, let's hope it's found.