chromiumembedded / cef

Chromium Embedded Framework (CEF). A simple framework for embedding Chromium-based browsers in other applications.
https://bitbucket.org/chromiumembedded/cef/
Other
3.38k stars 467 forks source link

a renderer process can't automatically exit without USE_SANDBOX buiding #3733

Closed cmf41013 closed 4 months ago

cmf41013 commented 4 months ago

Describe the bug building cefclient project without USE_SANDBOX,a cefclient renderer process can't automatically exit when terminate the first startup main cefcllient.exe process.

To Reproduce Steps to reproduce the behavior:

  1. building cefclient project without USE_SANDBOX,
  2. startup cefclient.exe process.
  3. force terminate the startup cefclient.exe( the ui type process) in the Task Manager.
  4. the Task Manager list remain a cefclient.exe( it has param type=renderer) , it make highly cpu using.

Expected behavior I want all cefclient.exe quit when the main cefclient process is terminated.

Screenshots image image

Versions (please complete the following information):

Additional context Does the problem reproduce with the cefclient or cefsimple sample application at the same version? Yes, it just appears in cefclient application.

Does the problem reproduce with Google Chrome at the same version? no

Add any other context about the problem here. Would you mind telling me whether it' gong to be fixed? Because I must build my application with MD flag, and it can't build with USE_SANDBOX. If it will not be fixed, I have to resolved it in my application.

bjdupuis commented 4 months ago

Seeing similar results being reported of a process not ending appropriately, and we aren't able to USE_SANDBOX either.

magreenblatt commented 4 months ago

Duplicate of #3614

cmf41013 commented 4 months ago

Duplicate of #3614

If building cefclient without USE_SANDBOX, It appears every time. But, if building with USE_SANDBOX, it never appears, and all processes can exit automatically when the startup process is forced to be killed in Task Manager. the key of these two different phenomena is whether it building with USE_SANDBOX. Why can it do well with USE_SANDBOX? @magreenblatt thanks

magreenblatt commented 4 months ago

@cmf41013 There are different code paths in Chromium for launching sandboxed and unsandboxed processes. See the discussion in #3614.

cmf41013 commented 4 months ago

@cmf41013 There are different code paths in Chromium for launching sandboxed and unsandboxed processes. See the discussion in #3614.

Will cef fix the problem ? or wait for the chromium fixing it ?