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

Deleting the RootCache directory after Cef.Shutdown doesn't work with the Chrome Bootstrap #4852

Closed
1 task done
Mik4sa opened this issue Jun 27, 2024 · 4 comments
Closed
1 task done
Labels
upstream These issues require fixing in the Chromium Embedded Framework(CEF) or Chromium.

Comments

@Mik4sa
Copy link

Mik4sa commented Jun 27, 2024

Is there an existing issue for this?

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

CefSharp Version

126.2.70

Operating System

Windows 11

Architecture

x64

.Net Version

.Net 4.8

Implementation

WinForms

Reproduction Steps

Checkout my example: https://github.com/Mik4sa/CefSharp.MinimalExample
I took the current MinimalExample, upgraded it to the latest version 126.2.70 and made a small change which reflects our situation: Com-In-GmbH-Co-KG-Consulting-Solutions/CefSharp.MinimalExample@28c9693

Expected behavior

Calling Cef.Shutdown should release all resources / handles so that deleting the RootCache directory works.

Actual behavior

After calling Cef.Shutdown some handles are still kept (for example to the debug.log file). The RootCache directory can't be deleted.

Regression?

This worked in the previous version 125.0.210. Also this works when changing back to Alloy Bootstrap

Known Workarounds

This works when changing back to Alloy Bootstrap

Does this problem also occur in the CEF Sample Application

Not Tested

Other information

In our application we want to delete the custom configured RootCache directory. Doing so worked until 126.2.70. With this version and the Chrome Bootstrap this is no longer possible. The reason is that there are still some handles to some files in that directory. For example the debug.log file. So the whole directory can't be deleted. I also noticed that way more files are written as before. Is this expected? Or is this maybe already the underlaying reason?

With Alloy Bootstrap:
image

With Chrome Bootstrap:
image

@amaitland amaitland added the upstream These issues require fixing in the Chromium Embedded Framework(CEF) or Chromium. label Jun 27, 2024
@amaitland
Copy link
Member

You'll need to raise your issue on https://github.com/chromiumembedded/cef/issues (post a link back here for reference)

@Mik4sa
Copy link
Author

Mik4sa commented Jun 28, 2024

Thanks. Wasn't sure if this is really upstream. Will do later this day :)

@Mik4sa
Copy link
Author

Mik4sa commented Jun 28, 2024

Do you think it's okay to write basically the same and that I'm coming from CefSharp? Or do I need to write more generally?

@amaitland
Copy link
Member

Closing as upstream. Please continue the conversation at chromiumembedded/cef#3726

@amaitland amaitland closed this as not planned Won't fix, can't repro, duplicate, stale Jul 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
upstream These issues require fixing in the Chromium Embedded Framework(CEF) or Chromium.
Projects
None yet
Development

No branches or pull requests

2 participants