[capableweb]

> I’ve seen this happen, but I don’t understand why that is possible. Chrome tabs are separate process, how can one tab freeze the whole browser even when running the worst code in existence?

Because if anything takes up 100% of CPU, other things starts being unresponsive as there is not enough CPU to go around. Happens easily when dealing with concurrency and parallism, which I'm guessing Figma happily uses.

[paulgb]

Chrome starts a process per tab. On a modern operating system, one process should not be able to starve another equally-privileged process of CPU, so it sounds like there is more going on here.

[fulafel]

This is not the case. Maybe people have already forgotten what using computers was like when everyone had only 1 core, but having a few desktop apps pegging their share of cpu doesn't hurt interactivity much even on single-core computers.

[MBCook]

All the other apps are fine. It’s whatever browser is trying to load Figma that freezes.

[failuser]

I’ve had a mouse cursor move slowly when doing some tasks in Chrome. And all other apps barely reacting. Still a mystery to me. I hope that was not a sign of some backdoor being installed through a Chrome vulnerability.

[failuser]

This should not be the case even on a single CPU machines that run interactive jobs. This is a shoddy process scheduling work.