Sam, there's currently quite a large (and growing) number of new filed [bugs](https://bugzilla.mozilla.org/buglist.cgi?list_id=16629781&longdesc_type=allwordssubstr&resolution=---&chfieldfrom=2023-06-01&query_format=advanced&chfield=%5BBug%20creation%5D&longdesc=TypeError%3A%20can%27t%20access%20property%20%22spec%22) that all seem to have at least this line in the log: `JavaScript error: resource:///modules/AsyncTabSwitcher.sys.mjs, line 1187: TypeError: can't access property "spec", tab.linkedBrowser.currentURI is null` eg of failure log: https://treeherder.mozilla.org/logviewer?job_id=421960149&repo=autoland&lineNumber=5342 Could the changes in this bug have affected these tests that are failing? They are several and across different components. There are also [these](https://bugzilla.mozilla.org/buglist.cgi?resolution=---&query_format=advanced&longdesc=uncaught%20exception%20-%20TypeError%3A%20this.mBrowser.urlbarChangeTracker&longdesc_type=allwordssubstr&list_id=16629759) new bugs that all have this failure line `uncaught exception - TypeError: this.mBrowser.urlbarChangeTracker.startedLoad is not a function at onStateChange@chrome://browser/content/tabbrowser.js:6670:47` eg of failure log: https://treeherder.mozilla.org/logviewer?job_id=421964403&repo=autoland&lineNumber=7355 Could you have a look over them and investigate what is going on? Thank you.
Bug 1819675 Comment 30 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Sam, there's currently quite a large (and growing) number of new filed [bugs](https://bugzilla.mozilla.org/buglist.cgi?list_id=16630375&longdesc_type=allwordssubstr&resolution=---&resolution=FIXED&resolution=DUPLICATE&chfieldfrom=2023-06-01&chfield=%5BBug%20creation%5D&query_format=advanced&longdesc=TypeError%3A%20can%27t%20access%20property%20%22spec%22) that all seem to have at least this line in the log: `JavaScript error: resource:///modules/AsyncTabSwitcher.sys.mjs, line 1187: TypeError: can't access property "spec", tab.linkedBrowser.currentURI is null` eg of failure log: https://treeherder.mozilla.org/logviewer?job_id=421960149&repo=autoland&lineNumber=5342 Could the changes in this bug have affected these tests that are failing? They are several and across different components. There are also [these](https://bugzilla.mozilla.org/buglist.cgi?resolution=---&query_format=advanced&longdesc=uncaught%20exception%20-%20TypeError%3A%20this.mBrowser.urlbarChangeTracker&longdesc_type=allwordssubstr&list_id=16629759) new bugs that all have this failure line `uncaught exception - TypeError: this.mBrowser.urlbarChangeTracker.startedLoad is not a function at onStateChange@chrome://browser/content/tabbrowser.js:6670:47` eg of failure log: https://treeherder.mozilla.org/logviewer?job_id=421964403&repo=autoland&lineNumber=7355 Could you have a look over them and investigate what is going on? Thank you.
Sam, there's currently quite a large (and growing) number of new filed [bugs](https://bugzilla.mozilla.org/buglist.cgi?list_id=16630375&longdesc_type=allwordssubstr&resolution=---&resolution=FIXED&resolution=DUPLICATE&chfieldfrom=2023-06-01&chfield=%5BBug%20creation%5D&query_format=advanced&longdesc=TypeError%3A%20can%27t%20access%20property%20%22spec%22) that all seem to have at least this line in the log: `JavaScript error: resource:///modules/AsyncTabSwitcher.sys.mjs, line 1187: TypeError: can't access property "spec", tab.linkedBrowser.currentURI is null` eg of failure log: https://treeherder.mozilla.org/logviewer?job_id=421960149&repo=autoland&lineNumber=5342 Could the changes in this bug have affected these tests that are failing? They are several and across different components. There are also [these](https://bugzilla.mozilla.org/buglist.cgi?longdesc_type=allwordssubstr&resolution=---&resolution=FIXED&resolution=DUPLICATE&chfieldfrom=2023-06-01&list_id=16630392&query_format=advanced&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&classification=Other&longdesc=uncaught%20exception%20-%20TypeError%3A%20this.mBrowser.urlbarChangeTracker) new bugs that all have this failure line `uncaught exception - TypeError: this.mBrowser.urlbarChangeTracker.startedLoad is not a function at onStateChange@chrome://browser/content/tabbrowser.js:6670:47` eg of failure log: https://treeherder.mozilla.org/logviewer?job_id=421964403&repo=autoland&lineNumber=7355 Could you have a look over them and investigate what is going on? Thank you.