1474580 - Firefox Developer Edition cannot access the internet on High Sierra

Status: RESOLVED WORKSFORME

(Firefox :: Untriaged, defect)

Description

[Jon]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:61.0) Gecko/20100101 Firefox/61.0
Build ID: 20180704003137

Steps to reproduce:

1. Upgraded from macOS Sierra to High Sierra
2. Started FF developer edition (my primary browser)



Actual results:

All pinned or remembered sites were unable to access the internet... spinning and then fail.  Chrome and 'regular' Firefox meanwhile are both able to successfully reach all of these sites. 

Downloaded a new version of Dev Edition (620b6 64-bit) but no love.

On the assumption that this might be a corrupted profile,  I created a new profile, but the problem remained with the Dev Edition


Expected results:

Should have been able to access the internet following the upgrade.

Comment 1

[Jon]

I noticed that about:profiles shows three profiles, one of which is supposedly in use by another application, but that profile doesn't exist (see attached screenshot) and there is not another application running that would be using that profile.

Comment 2

[Jon]

Attachment: about:profiles screenshot

Shows one apparently invalid profile, supposedly in use, but not on the system.

Comment 3

[ovidiu boca[:Ovidiu]]

Hi Jon,

I tested this on Mac OS X 10.13 with FF Dev Edition 62.0b7 (64-bit) and I can't reproduce your issue, please note that I didn't update form 10.12 to 10.13. 

If you open another FF version, let's say 61 release(https://www.mozilla.org/ro/firefox/new/) with the same profile, you can reproduce this issue? Also, it will be a good idea to try with Nightly 63 build https://nightly.mozilla.org/

The profile that doesn't exist, I think is a different issue. Maybe it will be a good idea to file in another bug for that.

Comment 4

[Jon]

Well... I installed a major High Sierra update yesterday (I'm now at 10.13.6) and when I tried Firefox Dev Edition just now (62.06b, the one I tried the other day), it worked without problem.

I'll revisit that extra profile (if it still exists) and raise another issues and will close this one for now.

Thanks.