-
Notifications
You must be signed in to change notification settings - Fork 27.9k
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
"Problems writing cached data file" #63605
Comments
@roblourens Can you check if that folder exists for you? |
That is weird... It means that we have generated cached data that we are now not accepting... This one is the file 'binding.js' for which we only happened to have one (the binding-npm-module) and which is used by spdlog... Two possibilities
both would cause a rejection and subsequent deletion of the file in question. Question is which of them causes this... @roblourens Can you reproduce this or does this just happen once in a while? Also cc @chrmarti who has reported a similar issue... |
This seems to happen quite regularly on my machine. |
Hm... This also happens when having an 'atomic' save logic (write to tmp, then rename) |
I see it today too, and the directory with the new hash does exist. |
… that filenames don't conflict, #63605
The problem must be that different instances of V8 read the same data but don't accept it. We don't really know why that is and what makes V8 reject data. I have pushed a change that adds a static name seed to each loader instance so that cached data isn't shared anymore between different loader-instances. This roughly adds 50 files to the cached data dir, but with that change I cannot reproduce this issue... |
Many errors regarding cached data in Insiders today:
The text was updated successfully, but these errors were encountered: