Scratch

meew0 wrote:

Maybe it's because you have so many scripts? You should delete unused / unimportant scripts...

The same error happens when you replace the first costume of the Scratch cat with only 1 pixel, resize to 65000 % and change the costume.

There is only one script, and each block is quite important    It's a really long script, but I hadn't been getting the script cut-off yet.

meew0 wrote:

coolstuff wrote:

meew0 wrote:

Maybe it's because you have so many scripts? You should delete unused / unimportant scripts...

The same error happens when you replace the first costume of the Scratch cat with only 1 pixel, resize to 65000 % and change the costume.

There is only one script, and each block is quite important    It's a really long script, but I hadn't been getting the script cut-off yet.

Hm... How many sprites are there?

Just one... It works by stamping (only a little though), and mostly uses lists. No colour sensing or anything...

mathematics wrote:

I think the only way to solve the problem is to make the project not-one-script (cut it into parts).

Yeah, I figured. Thanks for your help!

Are there any repeating scripts?

coolstuff wrote:

My amazing Pathing AI is rather script-heavy. I was trying to make a wonderful improvement to my script - and did so successfully. I like running my projects fullscreen, so I went into presentation mode, and the project didn't run as I had expected. So I *tried* going back into the script editor, but something strange happened. I got a wonky error message, and Scratch was stuck in a limbo between presentation and script editing mode:

I'm running Mac OS X v 10.6.3, but I'm running it on an older iMac. I was forced to force-quit the program, which then temporarily solved the issue. I've seen this reported before on the forums - so are there any particular ways to solve this problem? I'd like to be able to work happily on my projects without unexpected interruptions 

I got the same error on one of my programs that has a very long script in it.  It happens whether in Presentation Mode or not, and when the script is big enough it can happen as much as every time I edit it or drag a block around.  Also, the "options" presented in the pink box that pops up don't ever do anything.  This is on a newer PC running Windows 7.

One thing I found was that when I had to kill Scratch with the Task Manager, the Resource manager showed that it was still running.  If I launched Scratch again without first terminating the process in the Resource Manager, Scratch would lock up even quicker.  But if I killed it in the Resource Manager, too, I could "usually" run Scratch a little longer before it locked up.  I don't know if this is indicative of a memory leak or not, but it makes you wonder.

It is irritating to have "big plans" and be limited by the tool you are using, especially since it's not limited by the features or capabilities, but some funky memory error. 

Last edited by DB88 (2010-05-30 08:16:26)