Open Wowfunhappy opened 3 weeks ago
The situation is the same for me, running 10.11.6 El Capitan. Quite often, the new tab title responds the request and loads the website name, but nothing else happens, the tab remains blank. Happens particularly when I click on "Organize bookmarks," I can't access the bookmark page.
And, likewise, appears several times this line at the bottom of chrome://gpu :
ERROR:shared_image_manager.cc(325)] : SharedImageManager::ProduceMemory: Trying to Produce a Memory representation from a non-existent mailbox.
@Napolnrags Try launching Chromium with --in-process-gpu
as a workaround.
@Wowfunhappy
It looks as if the Terminal didn't really appreciate when I entered the instruction /Applications/Chromium.app/Contents/MacOS/Chromium --in-process-gpu
It responded
[999:1295:0624/101149.211223:ERROR:chrome_browser_cloud_management_controller.cc(161)] Cloud management controller initialization aborted as CBCM is not enabled. Please use the
--enable-chrome-browser-cloud-managementcommand line flag to enable it if you are not using the official Google Chrome build. Segmentation fault: 11
Huh! Very odd, the flag works for me.
Starting in Chromium legacy 124.0.6367.207.1, tabs sometimes stop working in a way I hadn't seen in a previous stable release. Instead of seeing the web page, you will only see a background color (often the background color of the website) and sometimes one or more large rectangles, which will sometimes blink and will sometimes move when the page is scrolled. Other tabs continue to work fine, but the broken tab will remain broken even if you navigate to a different URL. You can copy and paste the current URL into a new browser tab to fix things.
Whenever this happens, the following message is logged many times (visible at the bottom of chrome://gpu, or in the Terminal if Chromium was launched that way):
This is a reference to: https://github.com/blueboxd/chromium-legacy/blob/master.lion/gpu/command_buffer/service/shared_image/shared_image_manager.cc
Launching Chromium with the command line flag
--in-process-gpu
appears to prevent the problem from occurring. (This is not a great workaround, because if Chromium is launched with this flag and the GPU process does crash for any reason, it will bring down the whole browser.)I'm running OS X 10.9.5 Mavericks.