supermium: Random hangs with Version 121.0.6167.81 hotfix and Windows 7 SP1 x64

I just replaced the previous v118 with this one. Version 118 was having painting issues with the custom UI of the tabs area (the standard titlebar of the window was often visible in the first 35%-40% while the remaining tabs were still painted using the custom Chrome look). The problem was annoying but I could live with it. This version 121 with the hotfix does not have such problems but instead simply freezes (becomes non-responsive) soon after launching. When started with --enable-logging - the icon in the new tab becomes wrong, the page does not load at all and I can not even open DevTools.

305073255-dee60be9-c716-43f9-9b6d-8a3fd2f83c58

Z:\>d:\PROGRAM\Inet\Chrome\121.0.6167.81\chrome --enable-logging

Z:\>[5280:7760:0215/143458.842:ERROR:policy_logger.cc(156)] :components\enterprise\browser\controller\chrome_browser_cloud_management_controller.cc(16
1) Cloud management controller initialization aborted as CBCM is not enabled. Please use the `--enable-chrome-browser-cloud-management` command line f
lag to enable it if you are not using the official Google Chrome build.
[5280:7760:0215/143458.902:ERROR:gpu_process_host.cc(986)] GPU process launch failed: error_code=2
[5280:7760:0215/143458.913:ERROR:gpu_process_host.cc(986)] GPU process launch failed: error_code=2
[5280:7760:0215/143458.919:ERROR:gpu_process_host.cc(986)] GPU process launch failed: error_code=2
[5280:7760:0215/143458.924:ERROR:gpu_process_host.cc(986)] GPU process launch failed: error_code=2
[5280:7760:0215/143458.924:ERROR:service_worker_task_queue.cc(239)] DidStartWorkerFail ocaahdebbfolfmndjeplogmgcagdmblk: 5
[5280:7760:0215/143458.927:ERROR:gpu_process_host.cc(986)] GPU process launch failed: error_code=2
[5280:7760:0215/143458.929:ERROR:gpu_process_host.cc(986)] GPU process launch failed: error_code=2
[5280:7760:0215/143458.931:ERROR:gpu_process_host.cc(986)] GPU process launch failed: error_code=2
[5280:7760:0215/143458.932:ERROR:gpu_process_host.cc(986)] GPU process launch failed: error_code=2
[5280:7760:0215/143458.933:ERROR:gpu_process_host.cc(986)] GPU process launch failed: error_code=2
[5280:7760:0215/143458.933:FATAL:gpu_data_manager_impl_private.cc(448)] GPU process isn't usable. Goodbye.

With v118 I have only this minor issue - broken rendering of the titlebar and tabs:

shot-2

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 23 (3 by maintainers)

Most upvoted comments

I am about to rebase on upstream 122. Chromium upstream does a lot of things that mess with composition and hardware acceleration, as seen in 117 and 119 as well. I think this is another one of them, but I will be sure to test extensively to see if these issues are not actually issues to Chromium and then find a proper solution that does not involve removing hardware acceleration completely (Chromium abandoned hardware acceleration on Windows XP in 2013 - putting it back will be challenging but I hope to do that as well).

@thinkpad4 Looks like v119 is stable for me, too - it does not freeze like v121 and does not have the painting glitches in the titlebar/tabs panel like v118. I will stay with v119 for the moment.

@win32ss I am really THANKFUL for all your GIANT efforts to maintain this project! And I’m sad that I don’t know C++ enough to be able to help. If I can provide more detailed troubleshooting information in the future - just let me know how can I collect it. I am willing to contribute as much as I am capable of. I can’t speak for other people but for me personally, hardware acceleration is not so important as is the overall stability since I use Chrome mainly for web development (of business applications) so I don’t need WebGL or something like this. But I do need a non-hanging Supermium 😃