
Loading…
"Failed to load resource: net::ERR_FILE_NOT_FOUND" at launch #2
gorhill
commented
gorhill
commented
Never mind, it's caused by the fact that all the cached assets (as a result of an update op) are cleared when a new version is detected (because new versions ship with latest assets). Somehow chromium delete the cached file items, but the directory entry for these items still lingers a bit it seems. Anywho, the error case is all taken care by the extension, it will fall back to the non-cached version of the asset just as it is supposed to.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I often get this error at launch:
Appears to be related to auto update occurring at launch. Need to figure what is happening. Appears benign otherwise, extension works fine thereafter.