Page 2 of 2

Re: Setting cache path breaks extension use of local storage

PostPosted: Wed Apr 21, 2021 5:25 pm
by HarmlessDave
I downloaded the binary client for Windows 32-bit 89.0.18+gb36241d+chromium-89.0.4389.114 from Spotify.

The stock build CEF 79 does produce the error for me.

Code: Select all
C:\Temp\cef89\cefclient.exe --load-extension=C:\CEFClient\Widget  --cache-path="c:\temp\TestCache"


With just the load-extension, no error. With the cache path added, error.

Code: Select all
[0421/151550.523:WARNING:settings_storage_quota_enforcer.cc(229)] Failed to get settings for quota:IO error: .../LOCK: File currently in use. (ChromeMethodBFE: 15::LockFile::2)
[0421/151552.545:INFO:CONSOLE(15)] "Attempted to store data", source: chrome-extension://eghdanedkmffncahgghjdcjdogoefahc/widgetScript.js (15)
[0421/151552.546:INFO:CONSOLE(0)] "Unchecked runtime.lastError: IO error: .../LOCK: File currently in use. (ChromeMethodBFE: 15::LockFile::2)", source: chrome-extension://eghdanedkmffncahgghjdcjdogoefahc/widget.html (0)


The TestCache folde did exist and was empty. After running it has the files like LOCK and LocalPrefs.json

If it's working in your heavily modified CEF, perhaps one or more of your changes affects the storage code.

Re: Setting cache path breaks extension use of local storage

PostPosted: Thu Apr 22, 2021 12:54 am
by ndesktop
I will retest with the exact command line as you mentioned and modifications.
Unfortunately I am hitting an issue with the build of 4430, rebuilding now with VS2019.
After all is completed (hopefully with success) I will recheck ASAP.

Re: Setting cache path breaks extension use of local storage

PostPosted: Thu Apr 22, 2021 1:44 am
by HarmlessDave
Thanks! I appreciate the help, I've only ever made one change to the Chromium source years ago (patching a microphone bug back when we still used Flash), and I haven't really worked with the CEF source at all.

Re: Setting cache path breaks extension use of local storage

PostPosted: Thu Apr 22, 2021 12:52 pm
by magreenblatt
I'm able to reproduce this error with extension tests (starting with M91) so I've filed https://bitbucket.org/chromiumembedded/cef/issues/3114