Fixed in Jan 2026 release https://github.com/scratchfoundation/scratch-storage/pull/831 Please slide the slider until question mark first appears. Comment below at the number you see questions mark and state your OS and device memory. This is project tests the maximum number of costumes before Questions Marks appears: Window 11 x64 (16GB RAM + Nvidia Quadro k620 2GB) -Chrome: Show questions marks @ 1586 -Edge: Show questions marks @ 1389 -Firefox: No question marks @ 2048 -WebKit: No question marks @ 2048 -Scratch 3.0 win32 app: No question marks @2048 -Scratch 2.0 app: No question marks @2048 -Chrome Turbowarp: No question marks @ 2048 Sometime costume 2048 texture will display but lower costumes fail to display. Non-windows: Chromebook(2GRam): Show questions marks @ 1350 Arch Linux on Chrome: Show questions marks @ 1473 @speedy_chuck_365 Android: (2GB Ram): Show questions marks @ 1561 Android turbowarp: (2GB Ram): No question marks @ 2048 Android firefox: (2GB Ram): No question marks @ 2048 IOS 18 iPad (2GBRam): No question marks @ 2048 https://scratch.mit.edu/discuss/topic/821843/
Chrome only bug on sb3, sb2 works fine on chromium. Scratch VM creates async web request to download the 2048 images but chromium limits pending web requests to ~25mb (6000 requests with an avg header size [KAvgBytesPerOutstandingRequest] of 4400 bytes) The WebGL textures for each costume seems limited to ~1350 costumes before chrome runs out network request memory. ScratchVM creates unknown question mark image 64x64 for failed downloaded images. This project use bitmaps (png) as SVG appear to only generate the textures at runtime (first time the costume is referenced), so bitmap is more deterministic as all textures are instantiated at load time to better show the limitations of too many costumes. Scratch also has a max texture size (total pixel limit) of around 80 millions pixels as noted in Pokemon s01e01 This project started from a discussion on Why question marks of doom? has project that run at 30 fps on iOS but shows questions on chrome :-( Looking at the network trace it shows the failed images have an error "net::err_insufficient_resources" https://issues.chromium.org/issues/438924523 fails due to chrome limiting 25mb memory for pending net requests Scratch 2 works fine on chrome thx I think this work due to sb2 falls back files included in zip, so chromium doesnt hit the pending web requests limit. See sb2 fallback commit https://github.com/scratchfoundation/scratch-editor/commit/dc5f94c44f438b0caa77becce182816827473336 eg: Scratch-editor bug logged https://github.com/scratchfoundation/scratch-editor/issues/312
