-
-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tab Crash: Trying to Produce a Memory representation from a non-existent mailbox. #229
Comments
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 |
It looks as if the Terminal didn't really appreciate when I entered the instruction It responded |
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.
The text was updated successfully, but these errors were encountered: