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?
>>failus+(OP)
Figma is beyond chrome, it's a quantum app: it's both in a state that will lock up my pc while everyone on zoom waits for the screen to load and a journey in following designer's instructions: "no a bit more left, no actually right, ok go down, no up, ok back go the left a bit, ok here it is!", same vibe as rally racing lol
>>failus+(OP)
> 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.
>>capabl+Qb
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.
>>capabl+Qb
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.
>>seanth+r2
For #1: don’t use it in chrome, download the app (it seems like it takes advantage of the wrapper pretty well); for #2, just click on the designer’s name in the top corner to zoom your screen to theirs and let them drive for a second!
>>MBCook+ii2
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.