1332308 - A few "TypeError: this._panel is null" errors in debugger-view.js during devtools mochitest runs

Status: RESOLVED FIXED

(DevTools :: Debugger, defect, P3)

Description

[Ryan VanderMeulen [:RyanVM]]

Noticed this looking at a random Treeherder log recently.

https://treeherder.mozilla.org/logviewer.html#?job_id=70343178&repo=mozilla-inbound&lineNumber=1851

TypeError: this._panel is null: set hidden@chrome://devtools/content/debugger/debugger-view.js:883:7
clearView@chrome://devtools/content/debugger/debugger-view.js:904:5
clearViews@chrome://devtools/content/debugger/views/filter-view.js:206:5
clearSearch@chrome://devtools/content/debugger/views/filter-view.js:195:5
handleTabNavigation@chrome://devtools/content/debugger/debugger-view.js:791:5
_onWillNavigate@chrome://devtools/content/debugger/debugger-controller.js:362:5
emit@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/event-emitter.js:191:13
_setupRemoteListeners/this._onTabNavigated@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/client/framework/target.js:512:9
eventSource/proto.emit@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/client/main.js:130:9
onPacket@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/client/main.js:1017:7
send/<@chrome://marionette/content/server.js -> resource://devtools/shared/transport/transport.js:570:13
exports.makeInfallible/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/ThreadSafeDevToolsUtils.js:101:14
DevToolsUtils.executeSoon*exports.executeSoon@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/DevToolsUtils.js:42:19
send@chrome://marionette/content/server.js -> resource://devtools/shared/transport/transport.js:563:9
send@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/server/main.js:1498:5
receiveMessage@chrome://marionette/content/server.js -> resource://devtools/shared/transport/transport.js:761:7

Comment 1

[(Away)]

What controls whether this is available for starring? Does it need to say "Intermittent:" or something?

Comment 2

[Ryan VanderMeulen [:RyanVM]]

The intermittent-failure keyword on the bug

Comment 3

[Ryan VanderMeulen [:RyanVM]]

Why do you want this to show up on Treeherder? It's not a real failure and is going to just artificially inflate the OrangeFactor scores if people keep starring it. Better to yell at people who can fix it if it's causing you problems.

Comment 4

[(Away)]

I got an orange on Try with this error message that didn't repeat on a retrigger. If that's not the definition of an intermittent then what am I supposed to do?

Comment 5

[(Away)]

Ok sorry, on closer inspection I didn't realize that this wasn't the _actual_ failure message. (In my defense it was outnumbered 4:1 by this text)

Comment 6

[Julian Descottes [:jdescottes]]

This is creating some confusion when investigating intermittents and should be fixed.

Comment 7

[Jason Laster [:jlast]]

I believe this was fixed