Severe performance issues after update to 147.0.7727.55

[dadus33]

OS/Platform

Windows

Installed

https://ungoogled-software.github.io/ungoogled-chromium-binaries/

Version

147.0.7727.55

Have you tested that this is not an upstream issue or an issue with your configuration?

• I have tried reproducing this issue in Chrome and it could not be reproduced there
• I have tried reproducing this issue in vanilla Chromium and it could not be reproduced there
• I have tried reproducing this issue in ungoogled-chromium with a new and empty profile using --user-data-dir command line argument and it could not be reproduced there

Description

Severe performance issues after update to 147.0.7727.55

How to Reproduce?

1. Ensure chrome://settings/onStartup is set to Continue where you left off
2. Open the browser (in a profile where multiple tabs were previously opened - in my case 30)

Actual behaviour

The browser suffers from severe performance issues for several minutes after being opened.
Typing, scrolling or interacting with a page in any way becomes almost impossible.
This affects all tabs, weather it's an existing tab or a newly opened one.

Expected behaviour

The browser opens and I can interact with content without any performance issues.

Relevant log output

Additional context

After a few minutes (seems to average around 3 minutes from my tests) the issue resolves itself. Opening new windows doesn't bring it back either. However, completely closing the browser (so no chrome.exe process appears in task manager anymore) and opening it again brings back the issue.

Monitoring the process in task manager also shows little usage of resources, which stays roughly constant during the aforementioned 3 minute wait (and even after it, unless opening new tabs, for example). The exception to this is memory usage, which does increase steadily but just for the first few seconds after launch, during which tabs are loaded. The issue persists long after that.

Due to being affected by #562, I had to open the browser using the --disable-features=Glic flag. I couldn't test whether this still happens without the use of the flag, as the browser won't open at all in that case.

The issue did not occur on any of the previous versions of ungoogled-chromium I had installed. Re-installing the previous version (146.0.7680.177-1.1) makes the issue go away.

[void2012]

I am too lazy to create a separate issue but basically this update doesn't run on Windows 10 IoT LTSC at all for me (launching the chrome.exe spawns the process but it terminates in a split of a second, I don't know where is the debug output so I can't show it). The 146.x.x.x version works fine though.

[ruukulada]

This chrome version broke my local install entirely...had it installed through winget and caused hard crash on startup...no amount of deleting local user and install files could get that working again, switched to choco package and that got it running again

[bobsea123456]

147.0.7727.55-1.1 wont install properly never had a problem before. I tried .exe installer and zip portable. It will show installed in installed programs but wont open at all. I dont see any action during install just pops up windows safety are you sure you want to run and I even turn off windows security still wont work.

146.0.7680.177-1.1 Installed and runs normal,

void2012 post above is same problem I get a split second of a screen when trying to install but closes

[FriedGenera]

@void2012 @ruukulada @bobsea123456 is it related to #562?

[void2012]

@void2012 @ruukulada @bobsea123456 is it related to #562?

Yes! Sorry if didn't notice it

[bobsea123456]

@void2012 @ruukulada @bobsea123456 is it related to #562?

yes appears to be the same. I just installed 146.0.7680.177-1.1 and it works so I will try future version and skip 147.0.7727.55-1.1.
I am running win11 25H2

[dadus33]

@void2012 @bobsea123456 @ruukulada @FriedGenera
If following the workaround described in #562 (launching chrome.exe with --disable-features=Glic), do you notice the performance issues I mentioned (if you set your tabs to open where you left off)?
Curious to see if it can be reproduced

[dadus33]

Also, found something interesting regarding the performance issue: if there are 2 windows opened (where the first one is the one with the auto-opened tabs from last time chromium was opened) and the second one is a new, empty window (can even be an incognito window), the original window can be closed, and as long as the second window stays open (so the chrome.exe process is still visible in task manager), opening chromium again will NOT result in any performance issues. The tabs from last time still have to load, but the behavior is the same as in the previous version, where they load very fast.

This means the performance issue is not related to tabs being loaded, but to something totally separate that happens only in the first few minutes after starting the process.

[void2012]

I wonder what happened in v147 that nuked the whole thing like that. Also, does it happen only on Windows or somewhere else?

[Rusenche]

@dadus33 and @void2012, do these negative problems exist with the current versions of:

1. https://github.com/vpday/ungoogled-chromium-windows/releases/tag/147.0.7727.101-1.1/ - by @vpday;
2. https://github.com/1to9only/ungoogled-chromium-windows-x64-binaries/releases/tag/147.0.7727.101-1.1/ - by @1to9only?

[void2012]

Yes

[Rusenche]

void2012 3 minute ago:

Yes

If both options I showed give you the same problem, that's bad news. This means that in ~ 6 hours, when @Nifury's version (v.147.0.7727.101-1.1) is ready, it will have the same problem...

[void2012]

I don't have other platforms to test, is it upstream multiplatform chromium problem or just Windows ungoogled chromium problem?