TypeError: Cannot read property 'windowID' of null

[pedropauloalmeida700]

Hi.
First of all: thank you all for the great tool and service. Really like LastPass.

My Chrome Extension keep showing this error on Chrome Debugger Console:

Error in event handler for (unknown): TypeError: Cannot read property 'windowID' of null
at chrome-extension://hdokiejnpimakedhajhdlcegeplioahd/onloadwff.js:58:816001
at Object.handleResponse (chrome-extension://hdokiejnpimakedhajhdlcegeplioahd/onloadwff.js:58:757012)
at r (chrome-extension://hdokiejnpimakedhajhdlcegeplioahd/onloadwff.js:58:783163)
at r (chrome-extension://hdokiejnpimakedhajhdlcegeplioahd/onloadwff.js:58:5475)

It happens every time any page loads. If I turn off the extension, the error goes away. I use many other extensions, but the error occurs even when ONLY LastPass extension is active.

Chrome: Version 68.0.3440.75 (Official Build) (64-bit)
OS: OSX Sierra 10.12.6

I hope someone from LastPass team is watching this forum.

[mrfleshka]

On every page i see this: Chrome Console Screenshot
This screen from google.ru page

I have chrome version 68.0.3440.75
And LastPass extension version: 4.16.0

[maco13449]

I can confirm problem this with the latest version of all major browsers on Ubuntu 18.04. Happening since yesterday (july 30, 2018).
Besides polluting the console, it doesn't seem to have any effect on the functionality of the extension.

[DeBrevan]

I'm having the same issue on Mac OSX.

Chrome Version 68.0.3440.75
And LastPass extension version: 4.16.0

And yes, no effect besides the error in the DevTools.

[jaredenglert]

Happening to me as well on Windows 10 / Chrome

[sjones01010608]

Confirmed behavior -- happening with devtools enabled in chrome:

Chrome
Version 67.0.3396.99 (Official Build) (64-bit)

LastPass
4.16.0

[QuietNoise]

Exact same for me.

[Andrius]

Same behaviour here.

[person2323]

Same here.

[pekahl116]

Thank god I found this post - I was starting to wonder where the heck I'd introduced this bug into my code at work. LastPass needs to fix this, asap. Is there a support email we can mail to?