1855358 - Tab crashes on Linux Nightlies earlier than 2021-06-10

Status: RESOLVED INVALID

(Firefox :: New Tab Page, defect)

Description

[Vinny Diehl]

I get a "Gah. Your tab just crashed." This only happens on about:newtab and any website that I try to load, as far as I can tell; other about pages load fine. I get no reports on about:crashes. Browser console shows the following errors when I try to load about:newtab:

Error when attaching target: Error: Connection closed, pending request to server1.conn0.contentProcess147798/console2, type startListeners failed

Request stack:
request@resource://devtools/shared/protocol/Front.js:292:14
generateRequestMethods/</frontProto[name]@resource://devtools/shared/protocol/Front/FrontClassWithSpec.js:46:19
startListeners@resource://devtools/client/fronts/webconsole.js:310:34
attachConsole@resource://devtools/client/fronts/targets/target-mixin.js:461:26
    baseFrontClassDestroy resource://devtools/shared/protocol/Front.js:103
    destroy resource://devtools/shared/protocol/Front.js:71
    destroy resource://devtools/client/fronts/webconsole.js:385
    destroy resource://devtools/shared/protocol/Pool.js:199
    baseFrontClassDestroy resource://devtools/shared/protocol/Front.js:107
    _onTargetDestroyed resource://devtools/shared/commands/target/target-command.js:285
    _emit resource://devtools/shared/event-emitter.js:226
    emit resource://devtools/shared/event-emitter.js:172
    emit resource://devtools/shared/event-emitter.js:324
    _onTargetDestroyed resource://devtools/client/fronts/watcher.js:70
    _emit resource://devtools/shared/event-emitter.js:226
    emit resource://devtools/shared/event-emitter.js:172
    emit resource://devtools/shared/event-emitter.js:324
    onPacket resource://devtools/shared/protocol/Front.js:336
    onPacket resource://devtools/client/devtools-client.js:482
    send resource://devtools/shared/transport/local-transport.js:68
    makeInfallible resource://devtools/shared/ThreadSafeDevToolsUtils.js:103
    makeInfallible resource://devtools/shared/ThreadSafeDevToolsUtils.js:103

TypeError: can't access property Symbol.iterator, existingTargets is undefined

The problem is somewhere between 578715b6d3fcb21c0b61996347260ef9b119d0d2 and 8508c35e49793fbe402ad2a706a57fabd1c2b0c4 (dates 2021-06-09 and 2021-06-10). Artifacts are unavailable so I can't easily find the exact commit that fixes this crash, does anyone know anything about this before I go bisecting and building from source?

Comment 1

[Cieara Meador [:cmkm]]

Does this error occur in the latest Nightly? Can you provide more information on the need to debug this specific Nightly build, given its age of 2+ years old?

Comment 2

[Vinny Diehl]

This is only an issue when using mozregression to find old commits (usually hunting for bugfixes), which is why I opened this bug in that component originally. I've resorted to booting into Windows if I need to go back that far in mozregression, but it'd be nice to be able to do it from Linux; is anyone able to do this successfully?

Comment 3

[:Gijs (back August 25; he/him)]

I'm a bit puzzled about this bug. You're effectively saying "Nightly 2 years ago is crashing for me on Linux" [but more recent ones are fine]. Those builds are, well, 2 years old, and so is the source code used to build them. Unfortunately our time machine is currently out of action so we cannot go back and make them work again...

(In reply to Vinny Diehl from comment #0)

The problem is somewhere between 578715b6d3fcb21c0b61996347260ef9b119d0d2 and 8508c35e49793fbe402ad2a706a57fabd1c2b0c4 (dates 2021-06-09 and 2021-06-10). Artifacts are unavailable so I can't easily find the exact commit that fixes this crash, does anyone know anything about this before I go bisecting and building from source?

pushlog link for convenience

There's no crash stack in comment 0 (the devtools bits are unrelated, or perhaps a consequence of the debugged process crashing) so it's pretty much impossible to say anything useful. It would probably be more helpful to have a real debug stack from gdb or lldb or similar. But either way, we cannot fix bugs retrospectively, so I'm going to close this out. If you have more info, asking on matrix may yield more useful information.