Loading Profile...
Hi,
As my extension is running all the time in the background, it generates a couple of hundred following errors in the background console in Chrome during the course of a day:
Unchecked runtime.lastError while running tabs.get: No tab with id: 268.
at chrome-extension://ppcdhlicbeamihibghpgknfmonbhmnii/js/api/monitor.js:1:1249
The tab id changes after several repetitions, so perhaps it is trying to somehow interact with the current tab. The name of source file and line number doesn't change.
There don't seem to be any other issues, and this happens even without me doing anything with the extension (the bg scope is checking for several kinds of webRequests and sends out messages to all tabs if certain conditions are met — and they shouldn't be met in most cases during my day, so I think that it is the "listening" to these and other messages is generating these errors.
My extension id is 57891 (I am looking at the prod version), if you need to check the bg code. It has several listeners.
Help get this topic noticed by sharing it on
Twitter,
Facebook, or email.
Twitter,
Facebook, or email.
Many "No tab with id: ###" error messages in background console in Chrome
-
Hello Anton,
I have installed your extension and am leaving it running to see if I can reproduce the errors. I'll let you know the results at the end of the day.Comment-
Shlomo (Official Rep) October 30, 2014 15:17Apologies, my computer crashed today so I did not manage to reproduce the problem. I will try again on Sunday.EditDeleteRemove
-
-
Anton October 30, 2014 15:44OK, thank you!EditDeleteRemove
-
-
-
-
-
I managed to narrow it down — these console errors in background scope appear when I open new tab in Chome, and start typing an address — a record in console log appears for each key stroke.
My wild guess is that typing an address causes Chrome to start polling for suggestions — perhaps this triggers the Crossrider monitor, yet the tab isn't technically loaded yet, and this results in "No tab with id: ..." error.- view 1 more comment
-
-
Shlomo, you are correct in one way, there is no effect on how the extension functions. On the other hand, Chrome displays numer of errors when you look at the Settings / Extensions page, so it gives a bad image of the extension for the customers, which is quite significant.
Thanks for looking into this. -
-
I have added the request to the dev team queue, tough it may be a while since the person who deals with it on the team is on vacation and I'm sure will be inundated upon their return.
-
-
-
EMPLOYEE
