[andrewmutz]

Interestingly, this website reliably crashes my firefox on linux while consuming 55GB of memory.

Claude's TLDR of what's causing the problem (may or may not be accurate): "That animation loop is almost certainly leaking memory: each time-step it draws new border geometry (GeoJSON/vector shapes) but doesn't free the old frames, so RAM climbs without bound. When you interact — especially auto-playing the timeline — the tab grows until it swallows all 62 GB of RAM + swap and the kernel kills it."

[vova_hn2]

I can confirm, my firefox on linux crashes immediately as well.

Curiously, the website works just fine in chrome on android.

Blink monopoly strikes again, I guess.

[sombragris]

No issues here on Linux, using Firefox 140.12.0esr under Slackware and Plasma 6.7.2 / Wayland

[vova_hn2]

I have 152.0 installed from flatpack on Fedora Kinoite 43 (Plasma 6.6.3 / Wayland)

Maybe it's a firefox bug that was introduced somewhere after 140? idk

[sombragris]

or perhaps, some Plasma bug was fixed in Plasma 6.7x. Who knows...

EDIT: Now I see you installed it via flatpak. That is also a source of endless inconsistencies and instabilities. So you should maybe try the native fedora rpm.

[vova_hn2]

This is so called "Atomic" (rpm-ostree based) Fedora, so flatpak is the native way to install applications

[sombragris]

Yeah, I thought that. Too bad, you just hit one of the (very few) disadvantages of immutable systems.

[hofrogs]

This page crashed my browser too. Opened the comments to see this, guess it's not a me issue.

[anti_pop]

Same for me (FF 152, Fedora Linux). Fired a bug report, just in case: https://bugzilla.mozilla.org/show_bug.cgi?id=2054268

[NoboruWataya]

No issues on FF on Linux here. No crashes or memory leaks as far as I can see.

[cyclotron3k]

Crashes my Firefox on Android too