Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to Remote Debug when using Chrome Runtime #4919

Open
1 task done
puresimmer opened this issue Sep 3, 2024 · 3 comments
Open
1 task done

Unable to Remote Debug when using Chrome Runtime #4919

puresimmer opened this issue Sep 3, 2024 · 3 comments

Comments

@puresimmer
Copy link

puresimmer commented Sep 3, 2024

Is there an existing issue for this?

  • I have searched both open/closed issues, no issue already exists.

CefSharp Version

127.3.50

Operating System

Windows 11

Architecture

x64

.Net Version

.NET Core 8

Implementation

WinForms

Reproduction Steps

If I set the CefSettings.RemoteDebugging = X and then try and debug remotely it is just a blank page or won't load.

Note, I am using Bog-standard Winforms and .NET Core (default MultiThreaded msg loop, no offscreen stuff etc). The code all works fine if I flip back to the Alloy runtime via CefSettings.ChromeRuntime = false

I was also able to duplicate in CEFSharp CefSharp.WinForms.Example.netcore source (Latest Master) by adding CefSettings.RemoteDebugging = X and confirming the same issue in the CEFSharp Example.

Thanks for a great project that I have been happily financially supporting monthly for years!

Shaun

Expected behavior

Should be able to point at localhost:[remote debugging port] and attach to Devtools

Actual behavior

Empty page

Regression?

I have used this for years. Only a regression on ChromeRuntime - still works on depracated Alloy path.

Known Workarounds

Use CefSettings.ChromeRuntime = false

Does this problem also occur in the CEF Sample Application

Not sure, I will need to add RemoteDebuggingPort code to it in order to test, as I don't see any way to test this using the off-the-shelf sample app.

Other information

No response

@puresimmer
Copy link
Author

Looking deeper in CEFSharp code, this could be an upstream issue in CEF, as it doesn't look like you do anything magical and CEF seemingly fully handles the implementation of RemoteDebuggingPort. I'll keep you posted on what I find.

Shaun

@amaitland
Copy link
Member

this could be an upstream issue in CEF,

See chromiumembedded/cef#3740

@puresimmer
Copy link
Author

I can't believe I didn't find that in all my spelunking. Please go ahead and close this. I'm sure I can make it work with "chrome://inspect" as Marshall suggested.

Thanks for the quick response, great project, and support as always.

Shaun

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants