Skip to content

Loading…

uBlock v5.5 - Chrome v38 Collected Errors #207

Closed
harshanvn opened this Issue · 6 comments

2 participants

@harshanvn

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!

image

µBlock> readRepoCopyAsset("%s") / onRepoFileError("%s"):
image

image

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

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

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

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

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

@gorhill gorhill added a commit that referenced this issue
@gorhill gorhill this fixes one part of #207 c0aadc1
@gorhill

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.

@gorhill

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.

@gorhill

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.

@gorhill

0b64dbf fixes the "No tab with id: x" error.

@gorhill

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.

@gorhill gorhill added a commit that referenced this issue
@gorhill gorhill this completes fix to #207 6e77cc3
@gorhill

Fix completed with 6e77cc3.

@gorhill gorhill closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.