I suddenly cannot use Snap! anymore. Usually it works. Whenever I try to use Snap! for the first 15 seconds, works fine, then after that, it lags then eventually freezes until I get this:
This happens in any scenario.
This is an important bug fix. Did this happen to you too?
Edit: This bug happens even if you don't do anything to Snap!.
Edit 2: This bug didn't appear in 9.2.18 version, so it must be a bug with the current version. It isn't a bug on my computer.
Are you saying that if you run
https://snap.berkeley.edu/versions/v9/snap.html
it doesn't crash?
What OS/Browser are you using
Another question is, how much ram do you have? I noticed that the screenshot says that it ran out of memory, leading me to believe maybe snap is just using more memory than your computer is capable of.
I ran into this problem yesterday
chrome, win10
Are you saying yours crashed in a similar fashion to @ten_6044 ?
My Snap! crashes from time to time when working with very big projects but not 15 seconds after launching it with no scripts
Linux Mint/Vivaldi
Also OK on Chrome but it's an older version 127.0.6533.88 than is available on Windows
Without doing anything, brave (chrome) says snap is using 46.5 MB of memory, and it's not crashing for me (because I have 16 GB of ram, and I'm not running much other than brave and a couple other tabs, including youtube).
The only reason I bring up memory, is because your screenshot says
Error code: Out of Memory
same, around 30 sec and crash
Confirmed Snap 10.0.10, Chrome.v129@Win10 after clearing the Local Storage/Service Worker.
Disabling GPU acceleration does not help.
Snap v9.2.17 works as expected
I can only reproduce this in Chrome canary on my Mac, but I'm expecting this issue to hit Macs in the next days. I've disabled the service worker in a desperate attempt to address this. Canary still crashes for me, when when I then hard-reload Snap (v10.0.11) in it (reloading while keeping the shift-key pressed) it does work reliably for me. Can you confirm this on Windows?
Yes, Snap 10.0.11 no problem so far (after ten minutes).
I don’t know if the following observation is connected, but who knows … I found with Snap! 10.0.11 (only version I tried) on Chrome (on an iPad) the Streams library is still v.1, whereas on Safari it has been v.2 for some time now. IMV this suggests software modules are not fully aligned between different browsers.
It's more likely you need to figure out how to clear all the cache in chrome.
Extra information:
So it's probably a bug with the Chrome version and Snap! version.
I reinstalled Chrome, turns out you’re right insofar as the library version is up-to-date now. What still baffles me is that initially (before reinstallation) the Snap! version was rapported as 10.0.11 and the Streams library was from an older version of Snap! However I now wonder if I actually saw what I thought I did.
It's probably that chrome was just caching the library files, but not the js files. I don't really know.
I do want to mention, all browsers on ios are just wrappers over safari (which do have the ability to add more stuff, like adblocking in brave). However, if you're in the EU, you do have access to other browser engines (not safari) on ios, all because the EU forced apple to allow it (but apple decided to be stupid, and only give it to people in the EU, and limit it outside the EU).
It appears to be a ServiceWorker problem. sw.js registration has been deactivated in V10.0.11, although the previous SW was still registered for the snap.domain berkeley.edu, with the possibly outdated content. Most browsers offer some UI to unregister SW in case of emergency (if forced cache clearing does not work).
Chrome> Debugger(F12)> Application> 
Service workers> Unregister
Libraries are stored in *.xml files and were intended to be cached by SW for PWA/off-line use.
Bernat and I have killed the service worker file on the server just now, but it still keeps showing up if you've previously used it. the PWA cache is the most stubborn and strange idea I've ever seen. Anyway, after spending most of last night and this morning working on this (and finding many weird things in the new Chrome, I don't know what they're doing at Google these days) we think we've got it running stable by disabling the service worker. I could go into details as to why we think that is, but since I'll be on vacation for the next 2 weeks I just wanted Snap! to run stable in broken browsers again, which seems to be the case right now. This means, that for the time being installing Snap! as a Chrome app (PWA) is no longer going to work. We hope that's the lesser evil for now. Thanks for the quick test and confirmation, Dariusz!