Improve Scratch's memory management.

samq64

potatophant wrote:
samq64 wrote:
potatophant wrote:
samq64 wrote:
got a BSOD when trying to load the project in Scratch on my 8GB Windows PC.
that shouldn't happen with these kinds of things. ever. your computer has something wrong.
It was working fine until I tried to close Firefox…
did you get the screen with ":( your computer has ran into a problem and had to restart"?

Yes, but only for about 5 seconds, and then it automatically restarted itself.

Codingfairy07

Full support.
I want to load big projects easier on mobile without having to use forksphorus player.

Last edited by Codingfairy07 (Aug. 5, 2021 22:27:00)

Chiroyce

bump

101Corp

I have a PC with a GTX 1660 Super, G11 Core i7, 256GB SSD, and 16GB of ram. Wonder what would happen if I tested it…
Also, I tried using my GTX on a 3D game on Scratch. Seems as the bottleneck for performance is Scratch. Hmmmm…..

BautistaConTodo

Support! It would be hecking easier to run projects in low memory ram devices like my 4gb laptop!

ScolderCreations

dhuls wrote:
bump

Chiroyce

Update — Just look at the RAM that project takes on Safari

someone plz fix this asap aaa

Venatus_123

browser crash in this trash can
My browser / operating system: Android Linux 4.4.4, Opera 58.4.2878.56737, No Flash version detected;

gdpr5b78aa4361827f5c2a08d700

samq64 wrote:
Yes, but only for about 5 seconds, and then it automatically restarted itself.

something is very wrong with your computer.

Xolay

Chiroyce wrote:
Update — Just look at the RAM that project takes on Safari

someone plz fix this asap aaa

I thought that in Safari your tab would be reseted automatically. Since it's an iOS

Last edited by Xolay (Aug. 27, 2021 13:21:34)

Chiroyce

Xolay wrote:
I thought that in Safari your tab would be reseted automatically. Since it's an iOS

I use macOS, and it did eventually reload after 27GB

Last edited by Chiroyce (Aug. 27, 2021 13:29:03)

8ed

support

Last edited by 8ed (June 29, 2023 04:11:42)

Quantum-Cat

8ed wrote:
support

Why do you support? Please be constructive.

PGBFLITE6373

SUpport. i check out the prodect and my cpu was screaming. it was taking up the sameamount as if i was playing a game like bloons tower defence 6.

hello_smile

Full support. This is outrageous. I am using a device with 450 MB of RAM, and this makes it impossible to log into Ocular, as I cannot comment on the auth project..

dd if=turbowarp/scratch-vm of=llk/scratch-vm

This should be maximum priority.

Jonathan50

This is a bit similar to this suggestion. React is a pertinent software bloat factor, and I think this is one too (but I haven't seen anybody else mention it). Also, upscaling images.

Last edited by Jonathan50 (Aug. 28, 2021 01:52:25)

Chiroyce

Jonathan50 wrote:
This is a bit similar to this suggestion.

Oh dear - it was actually closed

Paddle2See* wrote:
Thanks for all the helpful feedback on this! We'll continue to evaluate our design choices as time and resources allow.

The original post had some good suggestions about the technology behind Scratch 3. Our design team has had time to review those suggestions and follow up on what made sense to them, from a design standpoint. Recently, the topic just seemed to be acting as a lightning rod for a variety of unconstructive complaints - probably because of the non-specific topic title. Forcing new topics should help us stay on point, hopefully.

Venatus_123

Support
it just waste of data
and it makes browser crash

heres a screenshot

loading that project in 8gb ram computer
edit: My browser / operating system: Windows NT 10.0, Chrome 92.0.4515.159, No Flash version detected

Last edited by Venatus_123 (Aug. 28, 2021 05:28:52)

Jonathan50

potatophant wrote:
support, this is actually ridiculous, and scratch's current system is a terrible way of handling assets in memory. it would be better to load and unload assets as they're needed, similar to how unity, unreal, or pretty much any respectable game engine out them. this might take a bit of work, but it really should be done since this kind of thing is pretty much essential for something like this.

I don't think it makes sense to load assets as needed; after all, the project works OK with Scratch 2 and Forkphorous (and see what quasarNebula wrote.) Either a JavaScript reference exists to an asset, or it will have to be downloaded (or decompressed from the archive or whatever if it's offline.) Notice that the OP doesn't say what happened when the project finally loaded, if it ever did; and I believe there isn't anything wrong with how Scratch 3 represents assets.

Rather the problem must be with how Scratch loads assets, particularly bitmaps: instead of merely making a WebGL texture from the bitmap, it turns the entire PNG-encoded bitmap into a base64 data URI so that it can stick it onto a canvas, and from there makes a WebGL texture; and it uses promises to (I believe) load them in parallel rather than one at a time. (Therefore, I guess, the memory required is basically proportional to something between the size of one asset and the total size of all of them (but far worse because of the data URI stuff) rather than just proportional to the size of the greatest asset.) Furthermore, since it's a Scratch 2 project, it scales each bitmap it loads up for no good reason… See load-costume.js.

Hypothetically if the project finished loading, its memory consumption would be more normal.

So the problem should be pretty easy to fix.

Last edited by Jonathan50 (Aug. 29, 2021 06:17:56)

SDFTDusername

even though i dont get this problem i support, it even might make loading a project faster!

Discuss Scratch