search

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

Unable to use differently name CEF sub processes with Chrome runtime #3712

Closed BrianAndersonMozenda closed 5 months ago

BrianAndersonMozenda commented 5 months ago

Describe the bug We are having trouble getting the chrome runtime to work with a differently named sub process executable. Is that supported? If not, are there plans to support that? We don’t have any trouble if we are using the alloy runtime.

https://github.com/chromiumembedded/cef/issues/3290 has been closed which made us believe that this should be supported. https://github.com/chromiumembedded/cef/issues/3685 "browser_subprocess_path" marked as DONE also makes us believe that it should be supported.

To Reproduce Steps to reproduce the behavior:

  1. Try to pass in browser-subprocess-path as a command line argument
  2. Make sure the application is using chrome runtime
  3. Run the application
  4. Assert application runs browser properly - Failure

Expected behavior Expect that named sub process executables should work.

Versions (please complete the following information):

Additional context Does the problem reproduce with the cefclient or cefsimple sample application at the same version? Yes

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

Add any other context about the problem here. We have also found that we have been having to copy the content of the resource folder into the release folder - The resource doesn't seem to be working for chrome runtime.

We have tried to submit this to the forum, however, we never receive the email verification. We have tried multiple times with no success.

amaitland commented 5 months ago

Try to pass in browser-subprocess-path as a command line argument

Did you try setting the path via CefSettings?

  • 125.0.15+g6da73a3+chromium-125.0.6422.41_windows32_beta_minimal

Have you tried with a stable M125 build?

BrianAndersonMozenda commented 5 months ago

@amaitland Thank you for the response. We have tried it with a newer build and the behavior is now different. There still might be an issue but we are going to work on trying to isolate it either to our code or CEFs. We will submit another issue if we find something more.

PS. What is the way to get access to the forum? We have tried but never receive the email verification.

magreenblatt commented 5 months ago

What is the way to get access to the forum? We have tried but never receive the email verification.

Please see https://github.com/chromiumembedded/cef/issues/2962#issuecomment-1465023905