The Lacros browser on ChromeOS will boot up faster in the future

If you own a Chromebook where the AUE date is about to expire you may have taken advantage of enabling the Lacros flags. By enabling Lacros flags on your Chromebook you can continue to use your device safely, even after the AUE date has expired.

This is great news for anyone who is worried about what to do once their device stops receiving updates. If you’re not in a position to go out and buy a new computer, enabling Lacros will add a few more years to your existing Chromebook or Chromebox.

How Lacros works is by separating ChromeOS and the browser, which by default are integrated. It’s this integration, which makes the Chrome browser start up instantly once you’ve entered your login details. At the moment you may have noticed that Lacros, where the browser and OS are separated; takes a little longer to boot up the browser once you’ve entered your login details. Thankfully, About Chromebooks has spotted something that will change all that.

Why is the Lacros browser slower?

Firstly, the Lacros browser works just fine once you’ve opened the browser on your Chromebook. You shouldn’t experience any difference in performance compared to using the Chrome browser, which comes with ChromeOS as standard.

The issue is more to do with how long it takes for the browser to boot up after you’ve launched the browser. The fact that ChromeOS is known for being an incredibly fast OS to use. It’s pretty easy to see how you could notice a difference when things start to slow down.

The Lacros browser is a Linux based version of Chrome. To ensure ChromeOS stays secure Linux based apps are launched within a container. When you launch your Lacros browser this process can make your browser open a little slower than you’d be expecting.

How will Google fix it?

Although the difference in booting up the Lacros browser compared to the standard Chrome browser is minimal. Any change in how quick the browser boots up may be noticeable.

The good news is Google isn’t about to let ChromeOS get a reputation for being slow. After all, this is one of the key selling points for the Chromebook, that it’s much faster than any other computer you may have used. How frustrating is it when you login to a Microsoft computer where it can take a further few minutes before any of your actions are registered? It’s one of the reasons why I stopped using MS computers. It’s utterly annoying!

To deal with this problem Google will be changing the code a little. If you have Lacros enabled on your Chromebook the script for running the browser will start as soon as you get to the login screen. You’ll not notice any difference as it will all be happening in the background. You’ll simply login with your password as normal and by the time you get to the ChromeOS desktop, the browser will be ready to open without any delay.

This is great news

This is what I love about Google and ChromeOS. Considering we have had the luxury of using ChromeOS for over ten years. It would have been really easy for Google to give us all the new features we’ve seen over the years, without considering how this would impact performance.

It’s pretty amazing really when you think about it. ChromeOS is far more advanced than it once was, yet we still enjoy a boot up time of about seven seconds. Once you’re at the desktop your Chromebook is ready for action. This is just one of the reasons why I love my ChromeOS computers so much.

It’s really good to see that Google isn’t about to let this change. Introducing Lacros is a huge task for the ChromeOS team, and it’s great to see they are making sure its implementation will not impact the performance we’ve come to expect when using our Chromebooks.

If you’ve not yet made the switch to ChromeOS or are looking for an upgrade. Take a look at my Top Ten Chromebooks in 2022.

1 thought on “The Lacros browser on ChromeOS will boot up faster in the future”

  1. My Acer C301 cbook hit AUE in July at ChromeOs 103, so I duly went to chrome://flags and enable lacros support: This worked fine the first time through, I had a handsome little yellow chrome in my shelf, but I needed to add the kids as other accounts as I had previously in Chrome 103. The add user button at the foot of the sign in page was grayed out so I couldnt follow the instructions. So I try to get back to safety, I clear all the chrome://flags, and try again from the top
    And now I have chrome://flags enabling lacros support
    And os://flags have grabbed all those enables e.g. “default browser” and “only browser” from chrome://flags
    but I don’t have a yellow lacros in my shelf
    And it would look like I’m going to have to power wash the family laptop and hope that I can start over. And they did warn me that this is experimental…

Comments are closed.