
Loading…
uBlock v5.5 - Chrome v38 Collected Errors #207
The home/repo file error can occur if your connection to internet dropped when uBlock tried to read the filter lists. Normally uBlock will write at the console which file couldn't be read -- "%s" should be the file name, but it looks like Chrome doesn't format the strings in their error collecting feature. Note that uBlock will make behind-the-scene requests to fetch the remote filter lists, so if you have HTTPSB installed and it blocks behind-the-scene requests, uBlock will fall back loading the local version of the filter lists.
The "No tab with id" seems new with Chrome 37, I don't see it on Chrome 34. It's benign, but I wonder why this happens. Looks like they changed the behavior of the API in there.
Re. chrome.tabs.get() error, I filed an issue with Chromium devs: http://code.google.com/p/chromium/issues/detail?id=410868
Edit: I was wrong, there is no issue with Chromium, I forgot I had another call to chrome.setIcon(), which was unguarded, unlike the other.
readRepoCopyAsset / onRepoFileError etc. can occur under normal circumstances, so what I will do is craft an error string which is more useful to the user.
Hi,
Updated uBlock to v0.5.5 by clicking "Update Extensions Now". Update was successful and it is working as expected. However, chrome reported below errors..Not sure if its an issue or not. So, just created a bug for your review!
µBlock> readRepoCopyAsset("%s") / onRepoFileError("%s"):

Unchecked runtime.lastError while running tabs.get: No tab with id: 22

Uncaught SyntaxError: Failed to execute 'querySelectorAll' on 'Docum

Uncaught SyntaxError: Failed to execute 'querySelectorAll' on 'Docum

Uncaught SyntaxError: Failed to execute 'querySelectorAll' on 'Docum

Uncaught SyntaxError: Failed to execute 'querySelectorAll' on 'Docum
