CEF Renderer getting crashed after a memory spike to 1 GB

Having problems with building or using the CefGlue .NET/Mono binding? Ask your questions here.

Moderator: fddima

CEF Renderer getting crashed after a memory spike to 1 GB

Postby sravan19986 » Mon Oct 22, 2018 6:28 am

i was launching my website where it will load the images with good quality, when i continously zoom the images the renderer memory is getting increased to 1 GB and the cefglue application is crashing with the below call stack.
if i disable gpu memory is not increasing and not seeing Crash. but the scrolling performance becomes very slow.

External component has thrown an exception at Xilium.CefGlue.Interop.libcef.execute_process(cef_main_args_t* args, cef_app_t* application, Void* windows_sandbox_info)
at Xilium.CefGlue.CefRuntime.ExecuteProcess(CefMainArgs args, CefApp application, IntPtr windowsSandboxInfo) in C:\Users\310185755\Downloads\cefglue-2987\CefGlue\CefRuntime.cs:line 185
at Xilium.CefGlue.Demo.DemoApp.RunInternal(String[] args) in C:\Users\310185755\Downloads\cefglue-2987\CefGlue.Demo\DemoApp.cs:line 87
at Xilium.CefGlue.Demo.DemoApp.Run(String[] args) in C:\Users\310185755\Downloads\cefglue-2987\CefGlue.Demo\DemoApp.cs:line 52


Please refer below CEF logs

[1022/165403.343:VERBOSE1:pref_proxy_config_tracker_impl.cc(151)] 0720E338: set chrome proxy config service to 071F7160
[1022/165403.344:VERBOSE1:pref_proxy_config_tracker_impl.cc(278)] 0720E338: Done pushing proxy to UpdateProxyConfig
[1022/165403.346:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Google 'Pilot' log
[1022/165403.346:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Google 'Aviator' log
[1022/165403.346:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: DigiCert Log Server
[1022/165403.346:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Google 'Rocketeer' log
[1022/165403.346:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Symantec log
[1022/165403.346:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Venafi log
[1022/165403.346:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Symantec 'Vega' log
[1022/165403.346:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: CNNIC CT log
[1022/165403.346:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: WoSign log
[1022/165403.346:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: StartCom CT log
[1022/165403.346:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Google 'Skydiver' log
[1022/165403.346:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Google 'Icarus' log
[1022/165403.346:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Izenpe log
[1022/165403.346:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Certly.IO log
[1022/165403.601:VERBOSE1:webrtc_internals.cc(99)] Could not get the download directory.
[1022/165404.137:INFO:cpu_info.cc(50)] Available number of cores: 4
[1022/165405.392:ERROR:child_thread_impl.cc(762)] Request for unknown Channel-associated interface: ui::mojom::GpuMain
[1022/165405.400:VERBOSE1:gles2_cmd_decoder.cc(3297)] GL_OES_packed_depth_stencil supported.
[1022/165405.407:VERBOSE1:gles2_cmd_decoder.cc(3297)] GL_OES_packed_depth_stencil supported.
[1022/165405.415:VERBOSE1:gles2_cmd_decoder.cc(3297)] GL_OES_packed_depth_stencil supported.
[1022/165407.260:VERBOSE1:script_context.cc(111)] Created context:
extension id: (none)
frame: 2CEA19EC
URL:
context_type: WEB_PAGE
effective extension id: (none)
effective context type: WEB_PAGE
[1022/165407.262:VERBOSE1:script_context.cc(111)] Created context:
extension id: (none)
frame: 00000000
URL:
context_type: UNSPECIFIED
effective extension id: (none)
effective context type: UNSPECIFIED
[1022/165407.262:VERBOSE1:dispatcher.cc(396)] Num tracked contexts: 1
[1022/165430.313:INFO:cpu_info.cc(50)] Available number of cores: 4
[1022/165430.359:VERBOSE1:gles2_cmd_decoder.cc(3297)] GL_OES_packed_depth_stencil supported.
[1022/165430.361:VERBOSE1:gles2_cmd_decoder.cc(3297)] GL_OES_packed_depth_stencil supported.
[1022/165430.370:VERBOSE1:dispatcher.cc(527)] Num tracked contexts: 0
[1022/165430.373:VERBOSE1:script_context.cc(120)] Destroyed context for extension
extension id:
effective extension id:
[1022/165430.373:VERBOSE1:script_context.cc(120)] Destroyed context for extension
extension id:
effective extension id:
[1022/165430.402:VERBOSE1:script_context.cc(111)] Created context:
extension id: (none)
frame: 528C19EC
URL:
context_type: WEB_PAGE
effective extension id: (none)
effective context type: WEB_PAGE
[1022/165430.405:VERBOSE1:script_context.cc(111)] Created context:
extension id: (none)
frame: 00000000
URL:
context_type: UNSPECIFIED
effective extension id: (none)
effective context type: UNSPECIFIED
[1022/165430.405:VERBOSE1:dispatcher.cc(396)] Num tracked contexts: 1
[1022/165433.836:VERBOSE1:dispatcher.cc(527)] Num tracked contexts: 0
[1022/165433.839:VERBOSE1:script_context.cc(111)] Created context:
extension id: (none)
frame: 528C19EC
URL:
context_type: WEB_PAGE
effective extension id: (none)
effective context type: WEB_PAGE
[1022/165433.839:VERBOSE1:script_context.cc(111)] Created context:
extension id: (none)
frame: 00000000
URL:
context_type: UNSPECIFIED
effective extension id: (none)
effective context type: UNSPECIFIED
[1022/165433.840:VERBOSE1:dispatcher.cc(396)] Num tracked contexts: 1
[1022/165433.842:VERBOSE1:script_context.cc(120)] Destroyed context for extension
extension id:
effective extension id:
[1022/165433.842:VERBOSE1:script_context.cc(120)] Destroyed context for extension
extension id:
effective extension id:
[1022/165441.439:VERBOSE1:dispatcher.cc(527)] Num tracked contexts: 0
[1022/165441.442:VERBOSE1:script_context.cc(111)] Created context:
extension id: (none)
frame: 528C19EC
URL:
context_type: WEB_PAGE
effective extension id: (none)
effective context type: WEB_PAGE
[1022/165441.442:VERBOSE1:script_context.cc(111)] Created context:
extension id: (none)
frame: 00000000
URL:
context_type: UNSPECIFIED
effective extension id: (none)
effective context type: UNSPECIFIED
[1022/165441.442:VERBOSE1:dispatcher.cc(396)] Num tracked contexts: 1
[1022/165441.443:VERBOSE1:script_context.cc(120)] Destroyed context for extension
extension id:
effective extension id:
[1022/165441.443:VERBOSE1:script_context.cc(120)] Destroyed context for extension
extension id:
effective extension id:
[1022/165441.711:VERBOSE1:mime_sniffing_resource_handler.cc(355)] To buffer: http://161.85.108.16/app/image.cs
[1022/165442.950:VERBOSE1:gles2_cmd_decoder.cc(3297)] GL_OES_packed_depth_stencil supported.
[1022/165442.965:VERBOSE1:gles2_cmd_decoder.cc(3297)] GL_OES_packed_depth_stencil supported.
[1022/165446.497:VERBOSE1:mime_sniffing_resource_handler.cc(355)] To buffer: http://161.85.108.16/app/image.cs
[1022/165446.791:VERBOSE1:mime_sniffing_resource_handler.cc(355)] To buffer: http://161.85.108.16/app/image.cs
[1022/165447.712:VERBOSE1:gles2_cmd_decoder.cc(3297)] GL_OES_packed_depth_stencil supported.
Last edited by sravan19986 on Mon Oct 22, 2018 7:41 am, edited 1 time in total.
sravan19986
Techie
 
Posts: 11
Joined: Fri Aug 28, 2015 4:52 am

Re: CEF Renderer getting crashed after a memory spike to 1 G

Postby fddima » Mon Oct 22, 2018 6:38 am

Hi.

Does it can be reproduced with cefclient?
If you use x86 build - then you should enable large address aware on resulting executable.
fddima
Master
 
Posts: 774
Joined: Tue Dec 07, 2010 6:10 am

Re: CEF Renderer getting crashed after a memory spike to 1 G

Postby sravan19986 » Mon Oct 22, 2018 7:44 am

Yes this issue is reproducible in x86 CEF client
Can you please explain how to do this "enable large address aware on resulting executable"
sravan19986
Techie
 
Posts: 11
Joined: Fri Aug 28, 2015 4:52 am

Re: CEF Renderer getting crashed after a memory spike to 1 G

Postby fddima » Mon Oct 22, 2018 7:48 am

sravan19986 wrote:Yes this issue is reproducible in x86 CEF client
Can you please explain how to do this "enable large address aware on resulting executable"


You can use `editbin /largeaddressaware your_executable` to set this executable flag. For more details you can see: Can I set LARGEADDRESSAWARE from within Visual Studio?.
fddima
Master
 
Posts: 774
Joined: Tue Dec 07, 2010 6:10 am

Re: CEF Renderer getting crashed after a memory spike to 1 G

Postby sravan19986 » Mon Oct 22, 2018 8:51 am

Thank you very much and it is working.. Can you please tell me with this what will be the max limit of Memory for 32 bit exe
sravan19986
Techie
 
Posts: 11
Joined: Fri Aug 28, 2015 4:52 am

Re: CEF Renderer getting crashed after a memory spike to 1 G

Postby fddima » Mon Oct 22, 2018 9:23 am

3GB is max user address space memory for 32 bit process with this mode (vs 2GB by default).
fddima
Master
 
Posts: 774
Joined: Tue Dec 07, 2010 6:10 am


Return to CefGlue Forum

Who is online

Users browsing this forum: No registered users and 1 guest