SharedImageManager::ProduceMemory: Trying to Produce a Memor

Having problems with building or using CEF's C/C++ APIs? This forum is here to help. Please do not post bug reports or feature requests here.

SharedImageManager::ProduceMemory: Trying to Produce a Memor

Postby Czarek » Mon Nov 11, 2024 5:05 pm

Anyone seen these errors? It causes rendering issues on Google website - seeing black and white boxes in browser.

Code: Select all
[4772:7116:1111/225852.558:ERROR:shared_image_manager.cc(356)] SharedImageManager::ProduceMemory: Trying to Produce a Memory representation from a non-existent mailbox.
[4772:7116:1111/225852.635:ERROR:shared_image_manager.cc(356)] SharedImageManager::ProduceMemory: Trying to Produce a Memory representation from a non-existent mailbox.
[4772:7116:1111/225852.635:ERROR:shared_image_manager.cc(356)] SharedImageManager::ProduceMemory: Trying to Produce a Memory representation from a non-existent mailbox.
..... lots of these messages repeating .....


It occurs with CEF 130 on Windows when loading Google website. Only when loading for the first time in session. On subsequent loads it renders everything okay.

I updated my Nvidia display driver, but it didn't help.

When I pass --disable-gpu flag then issue doesn't occur anymore.
Maintainer of the CEF Python, PHP Desktop and CEF C API projects. My LinkedIn.
User avatar
Czarek
Virtuoso
 
Posts: 1943
Joined: Sun Nov 06, 2011 2:12 am

Re: SharedImageManager::ProduceMemory: Trying to Produce a M

Postby ndesktop » Mon Nov 11, 2024 5:33 pm

Can it be this Brave issue? Looks like an nVidia problem.
Also this has some interesting comments.
ndesktop
Master
 
Posts: 845
Joined: Thu Dec 03, 2015 10:10 am

Re: SharedImageManager::ProduceMemory: Trying to Produce a M

Postby Czarek » Tue Nov 12, 2024 6:57 am

Thank you ndesktop.

Is --in-process-gpu flag supported by CEF? I tried it on Windows and it was crashing.
Maintainer of the CEF Python, PHP Desktop and CEF C API projects. My LinkedIn.
User avatar
Czarek
Virtuoso
 
Posts: 1943
Joined: Sun Nov 06, 2011 2:12 am

Re: SharedImageManager::ProduceMemory: Trying to Produce a M

Postby ndesktop » Tue Nov 12, 2024 11:09 am

--in-process-gpu looks supported.
What kind of crash is happening ?
ndesktop
Master
 
Posts: 845
Joined: Thu Dec 03, 2015 10:10 am

Re: SharedImageManager::ProduceMemory: Trying to Produce a M

Postby Czarek » Wed Nov 20, 2024 12:03 pm

@ndesktop Sorry for the late reply. Attaching screenshot with call stack of the crash when adding --in-process-gpu flag.

in-process-gpu crash.png
in-process-gpu crash.png (48.77 KiB) Viewed 731 times


Last messages from output:
Code: Select all
'phpdesktop-chrome.exe' (Win32): Loaded 'C:\Windows\System32\directmanipulation.dll'.
'phpdesktop-chrome.exe' (Win32): Loaded 'C:\Windows\System32\DriverStore\FileRepository\nv_dispsi.inf_amd64_48a80ad03ba4b589\nvwgf2umx.dll'.
'phpdesktop-chrome.exe' (Win32): Loaded 'C:\Windows\System32\DXCore.dll'.
The thread 0x3a14 has exited with code 0 (0x0).
'phpdesktop-chrome.exe' (Win32): Loaded 'C:\Windows\System32\DriverStore\FileRepository\nv_dispsi.inf_amd64_48a80ad03ba4b589\nvppex.dll'.
A breakpoint instruction (__debugbreak() statement or a similar call) was executed in phpdesktop-chrome.exe.
Maintainer of the CEF Python, PHP Desktop and CEF C API projects. My LinkedIn.
User avatar
Czarek
Virtuoso
 
Posts: 1943
Joined: Sun Nov 06, 2011 2:12 am

Re: SharedImageManager::ProduceMemory: Trying to Produce a M

Postby ndesktop » Wed Nov 20, 2024 5:16 pm

__debugbreak() means probably a (D)CHECK. Did you run with --enable-logging? Does it display something relevant other than "SharedImageManager::ProduceMemory" ?
ndesktop
Master
 
Posts: 845
Joined: Thu Dec 03, 2015 10:10 am


Return to Support Forum

Who is online

Users browsing this forum: Google [Bot] and 23 guests