News for hackers. Stuff that matters.
Re:Introduction to WebRender by CoreXtreme on Friday September 22, 2017 @01:35PM (#15314129)
Firefox has fixed all issues for me. I am about to dump Chrome, just give me fast startup time.
Re:Introduction to WebRender by emerged on Friday September 22, 2017 @02:06PM (#15314357)
Since startup time is important, why don't browsers just stay running but pause all threads? The memory consumption of a browser process without any tabs open is insignificant for the vast majority of users.
Re:Introduction to WebRender by MarkSweep on Friday September 22, 2017 @03:21PM (#15314979)
Google Chrome does this, I think by default. It starts the browser process when you log in to your computer, so when you open a browser window it is really fast.
Re:Introduction to WebRender by panarky on Friday September 22, 2017 @08:47PM (#15317320)
I just checked Chrome Beta on Ubuntu, Windows and OSX, and there are no Chrome processes running upon login.

No Chrome processes until I actually launch Chrome.

Can you verify?

Re:Introduction to WebRender by solnyshok on Saturday September 23, 2017 @01:21AM (#15318281)
it is a tick in the settings. something called "Continue running background apps.." in the settings-->advanced -- useful if you need google hangouts running in the background, or to get notifications from websites. I disable that though on all of my machines.