Code exception in contentscript.js (vAPI.setTimeout) when opening Chrome last session tabs that are partly cached

[laukstein]

I am running the latest uBlock Origin on latest stable Chrome, Win10.
I have noticed this issue for a while - when opening Chrome with last tabs session and some of the tabs url server is down, Chrome shows partly cached page (cached HTML, failing on all external files, JS, CSS, etc.) and console shows exception coming from chrome-extension://cjpalhdlnbpafiamejdnhcphjbkeiagm/js/contentscript.js

Uncaught TypeError: Cannot read property 'setTimeout' of undefined

fails in

this.tid = vAPI.setTimeout(this.callback, 20000);

where vAPI suddenly is undefined.

[uBlock-user]

failing on all external files, JS, CSS, etc.

Is suspendTabsUntilReady set to true ? Nvm, I can reproduce it even when set to false.

Edit: - I can reproduce it. Console spews this -

[gorhill]

What was the URL (as asked in the template) associated with that dev console?

[gorhill]

OK I can reproduce with @uBlock-user screenshot, which shows a page from github.com.

[uBlock-user]

I will just post the STR here.

1. Open chrome://settings/onStartup and select Continue where you left off

2. Open console, click on gear icon on the extreme right and tick Preserve Log

3. Visit github.com and once it completes loading close the browser.

4. Start Chrome again and the browser will connect to github.com and open the console as soon as you can to notice those errors being spewed.

[gorhill]

Looks like a Chromium issue to me.

The exception occurs at this line. Yet this line can't possibly be reached if vAPI is undefined -- which is why the exception occurs -- because it is unreachable due to this line not too far above. That code can execute if and only if vAPI is not undefined and of type object.

[uBlock-user]

Indeed, I cannot reproduce on Nightly.

[gorhill]

Actually, investigating further I find that this line is being executed when I launch the browser -- so correction, that seems to be a uBO issue. I need to keep investigating why this happens.

[gorhill]

While investigating #164, I find that the issue was also present with Firefox:

  NS_ERROR_NOT_INITIALIZED: contentscript.js:467 

[uBlock-user]

Did it appear in the console ? I didn't see that when I tried to reproduce twice.

[gorhill]

I can't remember what I did for the error to be reported, I was really focused on investigating #164. Now I am unable to find steps to reproduce for Firefox. But given this is the same exact line, I can say that Firefox suffered the same issue.

[laukstein]

I guess this still haven't landed in stable version. The exception still happens and I see now 1 additional exception in

var userStylesheet = vAPI.userStylesheet;

gorhill/uBlock@dc430f1 probably expected to fix it too.

Here the full log screenshot

Actually seems net::ERR_CONNECTION_REFUSED is caused by uBlock Origin, what means isn't related to Chrome cache at all.

[uBlock-user]

No not yet.

Actually seems net::ERR_CONNECTION_REFUSED is caused by uBlock Origin, what means isn't related to Chrome cache at all.

Also that will happen if you have suspendTabsUntilReady set to true

[peterschussheim]

@gorhill I am experiencing similar errors on all URLs, using Chrome Canary Version 71.0.3556.0 on macOS 10.13.6 (17G65). Would you like me to open a separate issue?

[gorhill]

What version of uBO are you using?

[peterschussheim]

uBO version 1.16.18

[gorhill]

The fix has not been released in a stable release yet, it's in the dev build.

[peterschussheim]

just did some basic tests with dev build and problem appears to be fixed. @gorhill thank you for the prompt response and your work on uBO 👍

[Mouvedia]

version: 1.16.21.101
browser: Canary 71.0.3556.0

@gorhill It doesn't work if the details' privacy mode switch is on.

[gorhill]

details' privacy mode switch is on

I don't know what that means. Please opened a new issue with proper steps to reproduce if you think there is an issue.

[gorhill]

I cannot: I am not allowed.

Of course you are allowed, otherwise you wouldn't be able to comment like you are doing now.

As said, I need steps to reproduce, I can't reproduce error message with a private window. Please open a new issue with all the required details in the template.

[Mouvedia]

Well I wasn't yesterday. It was limited to the contributors.

[gorhill]

You are confusing https://github.com/gorhill/uBlock/issues with here -- here is to file issues, the other is reserved to contributors -- as explained in the top opened issue.