Running Xilium.CefGlue.Client in the debugger

658 views
Skip to first unread message

Paul Tulou

unread,
Aug 2, 2012, 10:12:52 AM8/2/12
to cef...@googlegroups.com
I'm looking into running the Xilium.CefGlue browser in my application.  When working with the example client, I notice that if I run the built executable from the file system, everything works fine.  It loads up and displays the google.com website as it's supposed too.  However, if I set the client project as the startup project and then launch the debugger, the application starts, but the web page is never displayed.  The cursor just keeps spinning too.  During all this, I never see any exceptions.

Can someone explain why this is?  The reason I'm particularly interested is I am seeing the same behavior when I try to use CefGlue in my application, even when I'm running the app from the file system.  

Thanks for the help!
paul

Dmitry Azaraev

unread,
Aug 2, 2012, 10:19:49 AM8/2/12
to cef...@googlegroups.com
Hi.

It is happens because multiple process architecture affects. :)
Use or other subprocess child or use single process mode (check CefSttings properties).
--
Best regards,
   Dmitry                             mailto:fdd...@gmail.com

Paul Tulou

unread,
Aug 2, 2012, 10:40:22 AM8/2/12
to cef...@googlegroups.com
Hey Dmitry, thanks for your quick response.  Setting the CefSettings.SingleProcess setting to true fixed both of my use cases.  Thanks!  I notice that the comments on this property say that it is "less stable."  Has anyone seen any issues with this?  Are there scenarios I should be careful to avoid?

I tried also setting the BrowserSubProcessPath to the Xilium.Cefglue.Client.exe.  This did not seem to work.  From the comments on the property it seems that this would need to be a completely separate executable... which I don't have yet.  Is this approach considered "more stable" than the SingleProcess approach?

Dmitry Azaraev

unread,
Aug 2, 2012, 10:49:41 AM8/2/12
to cef...@googlegroups.com
SingleProcess mode is not officially supported by chromium team, and mainly used for debug purposes only by chromium team. So you must get decision for self is appropriate for you or no. Also single process mode have less isolation between renderer, so if renderer crashed it also crash main (browser) process.

Set BrowserSubProcessPath to cefclient.exe, for example.

fddima

unread,
Aug 7, 2012, 5:56:47 PM8/7/12
to cef...@googlegroups.com
Just, in addition to debugging: disabling visual studio hosting process also helps easily debug browser process.

Reply all
Reply to author
Forward
0 new messages