1497968 - Fennec perpetually startup-crashes after failed mochitest run

Status: RESOLVED INCOMPLETE

(Firefox for Android Graveyard :: Testing, defect, P3)

Description

[Botond Ballo [:botond] [back on May 21]]

STR:
  1. Do a Fennec build and install the local build.
  2. Run |mach mochitest <some-file>| without the
     computer and the phone being on the same network.
     (In my case, I forgot this was a requirement.)
  3. After a while, the page loaded on the phone shows
     a timeout error. At this point, Ctrl+C the
     |mach mochitest| command.

Actual results:
  Fennec goes on with its life and you can continue
  using it for normal browsing.

Expected results:
  Fennec is perpetually startup-crashing at this line:

  https://searchfox.org/mozilla-central/rev/65f9687eb192f8317b4e02b0b791932eff6237cc/netwerk/base/nsSocketTransport2.cpp#1372

Even some suggestions for how to recover from this state would be useful.

Comment 1

[Bob Clary [:bc] (inactive)]

Sounds MOZ_DISABLE_NONLOCAL_CONNECTIONS environment is set from whatever shell it is being launched from. Perhaps a pref is set as well.

Comment 2

[Botond Ballo [:botond] [back on May 21]]

(In reply to Botond Ballo [:botond] from comment #0)
> Even some suggestions for how to recover from this state would be useful.

(I recovered from this state by clearing the app data.)

Comment 3

[Bob Clary [:bc] (inactive)]

Can we close this then?

Comment 4

[Botond Ballo [:botond] [back on May 21]]

I think it's still a bug that we got into this state in the first case.

However, you can feel free to close it as WONTFIX if it seems like too much of an edge case to care about.

Comment 5

[Botond Ballo [:botond] [back on May 21]]

Happened again, even though this time my computer and phone were on the same network throughout. Seems to happen every time I want to transition from running mochitests, to running the browser normally?

Comment 6

[Geoff Brown [:gbrown]]

A speculative explanation:

1. Use 'mach mochitest' or another mach test command to start Firefox for Android. Firefox will be started with the MOZ_DISABLE_NONLOCAL_CONNECTIONS environment variable set.
2. Ctrl-C or otherwise break out of your mach command such that Firefox is left running. (Note that even if Firefox is not visible on your device, it might still be running in the background.)
3. Try to use Firefox manually on your device. If it is the same instance, it still has MOZ_DISABLE_NONLOCAL_CONNECTIONS in effect, so the first attempt to load a web page will crash.

If this is the case, work-arounds would include:
1. Run 'adb shell am force-stop org.mozilla.fennec_$USER' (use package name of your installed Firefox) after you break out of your mach test command. Then start a new Firefox instance.
2. On your host, set MOZ_DISABLE_NONLOCAL_CONNECTIONS=0 before running mach. Now non-local connections will be allowed, both during tests and in any accidental leftover sessions.

Comment 7

[BMO Automation]

We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.