Open GoogleCodeExporter opened 9 years ago
any updates on this? I am seeing this on Mac OS X 10.8.3
I am using chromedriver to connect to CEF
Driver info: chromedriver=2.9.248307,platform=Mac OS X 10.8.5 x86_64
Original comment by bino...@gmail.com
on 16 Jul 2014 at 1:42
This is a bug in Chromium and should be reported at http://crbug.com. CEF will
get the fix after it is fixed in Chromium.
Original comment by magreenb...@gmail.com
on 11 Feb 2015 at 8:03
A (non-informed) drive-by comment:
Note that Chromium enables IO before shutting down the renderer during the
teardown:
https://code.google.com/p/chromium/codesearch#chromium/src/content/browser/brows
er_main_loop.cc&sq=package:chromium&type=cs&l=822
// Teardown may start in PostMainMessageLoopRun, and during teardown we
// need to be able to perform IO.
base::ThreadRestrictions::SetIOAllowed(true);
BrowserThread::PostTask(
BrowserThread::IO, FROM_HERE,
base::Bind(base::IgnoreResult(&base::ThreadRestrictions::SetIOAllowed),
true));
#if !defined(OS_IOS)
if (RenderProcessHost::run_renderer_in_process())
RenderProcessHostImpl::ShutDownInProcessRenderer();
#endif
I wonder if the same needs to be done in the
CefContentRendererClient::RunSingleProcessCleanupOnUIThread
https://code.google.com/p/chromiumembedded/source/browse/trunk/cef3/libcef/rende
rer/content_renderer_client.cc
Also, note that the following code is not necessary:
// Clear the run_renderer_in_process() flag to avoid a DCHECK in the
// RenderProcessHost destructor.
content::RenderProcessHost::SetRunRendererInProcess(false);
The DCHECK in question is long gone.
Calling RenderProcessHostImpl::ShutDownInProcessRenderer() to do the job
(instead of doing it on your own) might help as well.
Original comment by aruslan@chromium.org
on 24 Feb 2015 at 2:35
Hi,
Same issue here. I tried to allow IO and several other things but without
success. It always leads to a crash when exiting Chrome_InProcRendererThread. I
must admit I am not comfortable with Chromium or CEF source code and I can't
find a clear way to fix that bug.
Marshall, you said this is a bug in Chromium but people from Google say this is
a bug in CEF. Who is right?
Original comment by jer...@fl4re.com
on 24 Feb 2015 at 9:51
@#3: Thanks for the suggestions, re-opening this issue to try them out.
@#4: Are you referring to something other than comment #3?
Original comment by magreenb...@gmail.com
on 24 Feb 2015 at 10:03
I tried #3 but I'm absolutely not sure what I did was correct. I also tried to
just comment base::ThreadRestrictions::AssertIOAllowed(); in
PlatformThread::Join() like it is done for Windows.
Original comment by jer...@fl4re.com
on 25 Feb 2015 at 11:09
Any progress on this?
Original comment by jerome.j...@starbreeze.com
on 9 Mar 2015 at 12:24
CEF is transitioning from Google Code to Bitbucket project hosting. If you
would like to continue receiving notifications on this issue please add
yourself as a Watcher at the new location:
https://bitbucket.org/chromiumembedded/cef/issue/1182
Original comment by magreenb...@gmail.com
on 14 Mar 2015 at 3:29
Original issue reported on code.google.com by
Alexande...@gmail.com
on 22 Jan 2014 at 9:58