JS Debugger crashes under mochitests

NEW
Unassigned

Status

5 years ago
4 years ago

People

(Reporter: mt, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
Bug 995417 causes gecko to crash if it tries to connect to an external host while running mochitests.  This is good, but the remote JS debugger still attempts to contact the update servers, triggering the crash.

This eventually crashes:

./mach mochitest-plain --jsdebugger foo

Comment 1

5 years ago
PSA: Use mach mochitest instead of mochitest-plain (it knows what the test flavors are)
(Reporter)

Comment 2

5 years ago
(In reply to Gregory Szorc [:gps] from comment #1)
> PSA: Use mach mochitest instead of mochitest-plain (it knows what the test
> flavors are)

That doesn't work for me, is it that new?
(Reporter)

Comment 3

4 years ago
More information:

243 INFO FATAL ERROR: Non-local network connections are disabled and a connection attempt to aus4.mozilla.org (63.245.217.219) was made.

about:config shows the following entries containing 'aus4':
app.update.certs.1.commonName;aus4.mozilla.org
app.update.certs.2.commonName;aus4.mozilla.org
app.update.url;https://aus4.mozilla.org/update/3/%PRODUCT%/%VERSION%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/update.xml
media.gmp-manager.certs.1.commonName;aus4.mozilla.org
media.gmp-manager.certs.2.commonName;aus4.mozilla.org
media.gmp-manager.url;https://aus4.mozilla.org/update/3/GMP/%VERSION%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/update.xml
(Reporter)

Comment 4

4 years ago
106 INFO FATAL ERROR: Non-local network connections are disabled and a connection attempt to tiles.up.mozillalabs.com (2406:da00:ff00::4b65:a18f) was made.

Every. Single. Time.
(Reporter)

Updated

4 years ago
See Also: → bug 1049688

Comment 5

4 years ago
Sounds like the jsdebugger isn't using prefs_general.js correctly (which have the appropriate prefs already stubbed out). That sounds like a better fix than anything related to bug 1049688.
You need to log in before you can comment on or make changes to this bug.