zlacker

>>imslav+(OP)
I have the displeasure of using Figma at my job. I have a very low opinion of anything that locks up my browser for multiple seconds (Chrome or Safari) whenever I open it in a tab.

Then it takes a few seconds to load the file, which I don’t care much about.

But locking my entire browser is inexcusable.

It’s nice they’re working on performance once you get going, but launch performance is abysmal for me (x86-64 Mac).

>>MBCook+ZD1
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+ME1
> 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+CQ1
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.