SEB not clearing cache on shutdown

[actionhenkt]

Hello,
We are using seb 3.9 and it fails to clean up the cache when we shut down SEB. We get this error log:

Says some file is still in use:

`# New client instance started at 2025-11-12 17:04:05.133

2025-11-12 17:04:05.473 [01] - WARNING: [Audio] Could not find an active audio device!
2025-11-12 17:04:07.612 [01] - WARNING: [BrowserApplication] The configured down- and upload directory does not exist! Falling back to the default directory...

2025-11-12 17:53:50.033 [01] - ERROR: [BrowserApplication] Failed to delete browser cache!

Exception Message: Kan geen toegang krijgen tot het bestand first_party_sets.db omdat het wordt gebruikt door een ander proces.
Exception Type: System.IO.IOException

bij System.IO.Directory.DeleteHelper(String fullPath, String userPath, Boolean recursive, Boolean throwOnTopLevelDirectoryNotFound, WIN32_FIND_DATA& data)
bij System.IO.Directory.Delete(String fullPath, String userPath, Boolean recursive, Boolean checkHost)
bij SafeExamBrowser.Browser.BrowserApplication.FinalizeCache() in C:\Users\appveyor\projects\seb-win-refactoring-6tj6ae97ro290h9u\SafeExamBrowser.Browser\BrowserApplication.cs:regel 246

Client instance terminated at 2025-11-12 17:53:50.076

`
It says a file "first_party_sets.db" is still in use by a process (i assume seb as it is in seb cache folder)
What impact does/can this have if the cache is not cleared properly ?

[dbuechel]

I have also come across the error message above, but according to my current state of knowledge it is negligible, as the rest of the cache (in my case) always has been deleted correctly.

However, I can't entirely judge the severity of its impact as I don't know the inner workings of the engine good enough. If that is a relevant matter to you, I recommend searching online and/or potentially asking in the upstream repositories of CefSharp / CEF with respect to the significance and purpose of the database file.

[dbuechel]

There appears to be a discussion with respect to the issue: cefsharp/CefSharp#4361. As already marked previously, this is an upstream issue and very likely negligible and we unfortunately do not have the time to implement the workaround (nor would it be desirable, IMHO).

[github-actions]

This issue is stale because it has been open for 28 days with no activity. It will soon be closed automatically if there are no updates.