Scratch

squeak is the scratch scorce code. I had this problem too.

trinary wrote:

Your computer may be overloaded or running too many programs.
Try compressing the images/sounds you are using in your project, or closing some of the programs which are running.

Scratch was the only program on, there are no sounds, The only images there were were the Scratch cat, and a 1 pixel big costume, and the stage completely white.

I think that it just can't handle the large script that was there
(it was a HUGE script)

puppymk wrote:

TorbyFork234 wrote:

I think that it just can't handle the large script that was there
(it was a HUGE script)

I saw it happen once with someone I know when they had almost no scripts.

But was the script that they had large? Mine took a long time to scroll all the way down.

jji7skyline wrote:

TorbyFork234 wrote:

puppymk wrote:

I saw it happen once with someone I know when they had almost no scripts.

But was the script that they had large? Mine took a long time to scroll all the way down.

Long scripts can kill memory in Scratch. Happened to me a few times.

Also, lots of backgrounds, or large backgrounds, can kill memory in Scratch.

This is why we need a 64-bit Scratch :3

What's "bit" (sorry, n00b at computers)

TorbyFork234 wrote:

jji7skyline wrote:

TorbyFork234 wrote:

But was the script that they had large? Mine took a long time to scroll all the way down.

Long scripts can kill memory in Scratch. Happened to me a few times.

Also, lots of backgrounds, or large backgrounds, can kill memory in Scratch.

This is why we need a 64-bit Scratch :3

What's "bit" (sorry, n00b at computers)

A bit is a yes/no, true/false, zero/one slot of memory on a computer.
There are two types of computers: 32-bit and 64-bit.

32-bit processors are able to go through 32 slots of yes/no, zero/one memory in a given time, whereas 64-bit ones can go through 64 slots in the same time. This means that they are quicker and can handle more memory.

Excessively long script blocks will definitely cause this problem.

Here are some tips to avoid crashing Scratch when you must work with long script blocks.

Apply these tips while on a sprite's Scripts tab that contains a long script block:

- Do not drag the scrollbar. Click the empty part of the scrollbar to scroll a page at a time.
- Pause a few seconds between clicks, especially on the scrollbar.
- Drag blocks SLOWLY and wait until Scratch responds before dragging long distances.
- MOST IMPORANT: break the large script block up into 2 or more pieces, make your changes, then put the block back together.
- SAVE OFTEN
- Avoid scrolling upwards. It's better to save and let Scratch reset you to the top of the page or to click onto another sprite and then back onto this one.
- Avoid editing text fields on blocks that are part of large script blocks. Try breaking the block out, make your edit, and then reattach it.
- Be efficient. Don't mouse over items unnecessarily. Try not to drag blocks over hotspots unnecessarily.

I'm hoping there's a way to start Scratch with more memory to give more headroom. Anybody know of a way?