You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is still an intermittent startup failure happening on Windows XP x86 with 126.0.6478.260 R6,
The previous version was the same.
Starting up the browser, it sometimes apparently crashes and no window appears.
It doesn't happen every time, I would say about one time in four.
When the problem happens, when the browser is run, either nothing appears to happen, or it appears briefly in the taskbar and then vanishes. Immediately running it again will often then apparently run correctly.
If the browser window does not open, there are still several chrome.exe tasks running in the Task Manager.
Sometimes it won't just start when it's tried again, and in that case these processes have to be manually killed before the browser will start again, and in that case it then usually does start correctly
The text was updated successfully, but these errors were encountered:
DaveH1
added
the
Critical bug
A bug that does break the browser, as in causing crashes or making it impossible to perform a task
label
Dec 17, 2024
Based on various reports from Windows XP users, some further internal changes will be needed, including the introduction of keyed events. This should improve stability.
There is still an intermittent startup failure happening on Windows XP x86 with 126.0.6478.260 R6,
The previous version was the same.
Starting up the browser, it sometimes apparently crashes and no window appears.
It doesn't happen every time, I would say about one time in four.
When the problem happens, when the browser is run, either nothing appears to happen, or it appears briefly in the taskbar and then vanishes. Immediately running it again will often then apparently run correctly.
If the browser window does not open, there are still several chrome.exe tasks running in the Task Manager.
Sometimes it won't just start when it's tried again, and in that case these processes have to be manually killed before the browser will start again, and in that case it then usually does start correctly
The text was updated successfully, but these errors were encountered: