Closed GoogleCodeExporter closed 9 years ago
What is your use case for this notification?
Original comment by magreenb...@gmail.com
on 3 Mar 2015 at 5:21
We experienced cases where the renderrer didn't start after a new browser have
been created. So we use a 'watchdog' to identify these cases. If the callback
in the patch is not called within a <threshold> time - we restart the browser
process.
Original comment by amitkan...@gmail.com
on 3 Mar 2015 at 6:49
@#2: Interesting. Does the problem reproduce with current branches (2171+?) Do
you have any information (error messages, etc) on why the renderer process is
failing to launch?
Original comment by magreenb...@gmail.com
on 3 Mar 2015 at 6:56
We didn't experience the problem on 2171+ (we'll keep you posted about these
branches) - but it's crucial for us to have this ability, even if it'll never
be used.
Original comment by amitkan...@gmail.com
on 3 Mar 2015 at 7:02
@#4: The reason I asked is that it would be good to fix the underlying problem
if possible. If it still occurs for you please add a new CEF issue with
whatever information you're able to gather.
Original comment by magreenb...@gmail.com
on 3 Mar 2015 at 7:13
Thanks for the patch. New CefRequestHandler::OnRenderViewReady method added in
trunk revision 2055.
Original comment by magreenb...@gmail.com
on 9 Mar 2015 at 9:05
Original issue reported on code.google.com by
amitkan...@gmail.com
on 3 Mar 2015 at 10:31Attachments: