Switching networking Location on OS X causes crash

UNCONFIRMED
Unassigned

Status

()

Core
Networking
P3
normal
UNCONFIRMED
3 years ago
7 months ago

People

(Reporter: Simon Howes, Unassigned)

Tracking

({crash})

37 Branch
x86
Mac OS X
crash
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [necko-backlog])

Attachments

(4 attachments)

(Reporter)

Description

3 years ago
Created attachment 8543145 [details]
crash.txt

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:37.0) Gecko/20100101 Firefox/37.0
Build ID: 20141231030205

Steps to reproduce:

When changing the Location for network settings in OS X, crash reporter opens with a crash log. Location also does not change, to change the browser has to be quit, change the Location and reopen browser. See attached file for log.
I couldn't reproduce this in 38.0a1 (2015-01-12) OS X 10.9.5, OS X 10.10.

Please check if the issue occurs using Firefox in safe mode (with your addons disabled):
http://support.mozilla.com/kb/Safe+Mode

And on a new, empty profile:
http://support.mozilla.org/en-US/kb/Managing-profiles#w_starting-the-profile-manager
Component: Untriaged → Geolocation
Flags: needinfo?(simon.bugzilla)
Product: Firefox → Core

Comment 2

3 years ago
This sounds like you are talking about "network location", as in a profile of default network connections. By "location does not change", do you mean Firefox cannot access some site, because it uses the wrong network connections?

If I'm correct this is not related to geolocation, but to our networking stack instead.

Comment 3

3 years ago
(In reply to Hanno Schlichting [:hannosch] from comment #2)
> If I'm correct this is not related to geolocation, but to our networking
> stack instead.

Yes, the crash report points to this (NetworkLocation), so I'm moving this. OTOH, this seems mac-specific, so I'm CC'ing a bunch of our mac folks to see if they have ideas.

Simon, it would be useful to have a Firefox crash report (about:crashes will give you this after the Firefox crash reporter has come up); the stack in the .txt here seems to be the networking change stack, not the Firefox crash stack...
Component: Geolocation → Networking
Keywords: crash, stackwanted

Updated

3 years ago
Summary: Switching networking Location on OX X causes crash → Switching networking Location on OS X causes crash
(Reporter)

Comment 4

3 years ago
Created attachment 8548244 [details]
Video showing crash

There is no crash logged in about:crashes.

Yes, tried a clean profile. 

Attached is a video. The first attempt is with Quicktime as the foreground app, location switches fine, I then switch to Firefox as the foreground app and do the same task again, crash reporter opens. Also, the location fails to switch.
Flags: needinfo?(simon.bugzilla)
> When changing the Location for network settings in OS X

This is going to be difficult to diagnose, since most people only have one "location" in the Network control panel, which is by default set to use DHCP.

Please give us as much information as you can about what Locations you have, and how they're configured.

> crash reporter opens with a crash log

Please attach a copy of at least one of these crash logs.  You should be able to find them in ~/Library/Logs/DiagnosticReports/ (or perhaps /Library/Logs/DiagnosticReports/).

> The first attempt is with Quicktime as the foreground app

I assume you mean the QuickTime Player.  Is this correct?

> Attached is a video.

I can find no useful information in your video.  But then videos of bugs almost never contain useful information.  And in any case a detailed set of (written) steps to reproduce is always much more useful -- presuming it's well-written.
> Please attach a copy of at least one of these crash logs.

Oops, I see you've already done this.
> attachment 8543145 [details]

The crash takes place entirely in system code.  This probably means that it's at least partly an OS bug.
I've been unable to reproduce so far. You mention that a clean profile doesn't fix it. Is this also true for safe mode (see comment 1)?
> attachment 8543145 [details]

Looking more closely, this log has several interesting/puzzling details.

It's inaccurate -- what it calls thread 0 can't possibly be thread 0.

Only one thread is listed.

There's this annotation:

> Application Specific Information:
> crashed on child side of fork pre-exec

Could it be that the plugin-container process is crashing before the OS has been able to rename it from "firefox"?  (Immediately after forking, the child process has the same name as the parent.)  And why is "fork" mentioned, since we don't use it (we use posix_spawn() instead)?
(Reporter)

Comment 10

3 years ago
>This is going to be difficult to diagnose, since most people only have one "location" in the Network control panel, which is by default set to use DHCP.

>Please give us as much information as you can about what Locations you have, and how they're configured.

The location I switched to in the video 'DNS' is simply a configuration for OpenDNS.

>You mention that a clean profile doesn't fix it. Is this also true for safe mode (see comment 1)?

Safe mode appears to switch locations fine. No crash reporter opens and locations change fine.

> I assume you mean the QuickTime Player.  Is this correct?

Yes, Quicktime player.
(In reply to Simon Howes from comment #10)
> >You mention that a clean profile doesn't fix it. Is this also true for safe mode (see comment 1)?
> 
> Safe mode appears to switch locations fine. No crash reporter opens and
> locations change fine.

This would indicate that an addon may be interfering here. Could you try disabling them one by one to identify the addon that causes the crash?
> The location I switched to in the video 'DNS' is simply a configuration for OpenDNS.

This isn't much information.

So, then, do you have two "Locations", one set up for OpenDNS and the other "Automatic" (with the default settings)?  And is your OpenDNS "Location" the default settings plus OpenDNS's two DNS servers, as per https://support.opendns.com/entries/58244194-OSX-Yosemite?
With my own networking set up as per comment #13, and testing with today's mozilla-central nightly on OS X 10.10.1, I'm unable to reproduce this bug (by switching between my Automatic and OpenDNS locations, then clicking Apply).

As Stephen asked, please try disabling your extensions one by one, to see if one of them is somehow involved.

Also let us know if changing the page you're visiting (in Firefox) makes a difference.

For what it's worth, the machine I'm testing on has a WiFi internet connection.  Does yours?
(Reporter)

Comment 15

3 years ago
Created attachment 8548341 [details]
Screenshot of DNS settings

> This isn't much information.

Apologies. You create a new location, then simply configure the DNS settings. It also crashes for changes in proxies, or VPNs etc.
(Reporter)

Comment 16

3 years ago
>I'm unable to reproduce this bug (by switching between my Automatic and OpenDNS locations, then clicking Apply).

I guess you are doing it via System Preferences? Please do it via the Apple logo in the top left, and make sure the browser is the foreground app. Possibly the way you are doing it System Prefs is in the foreground.
(Reporter)

Comment 17

3 years ago
>As Stephen asked, please try disabling your extensions one by one, to see if one of them is somehow involved.

Ok, I have moved all extensions from '~/Library/Internet Plug-Ins' and '~/Library/Internet Plug-Ins', loaded the browser, the only listed extension is:

OpenH264 Video Codec provided by Cisco Systems, Inc 1.1

Still get a crash reporter appear, location does not change.

It doesn't matter which web site, it even crashes on about:blank
(In reply to Simon Howes from comment #17)
> >As Stephen asked, please try disabling your extensions one by one, to see if one of them is somehow involved.
> 
> Ok, I have moved all extensions from '~/Library/Internet Plug-Ins' and
> '~/Library/Internet Plug-Ins', loaded the browser, the only listed extension
> is:
> 
> OpenH264 Video Codec provided by Cisco Systems, Inc 1.1
> 
> Still get a crash reporter appear, location does not change.

Interesting. Could you go through all the troubleshooting steps in the kb article in comment 12 and see at what point the crashes stop? Thanks!
> It also crashes for changes in proxies, or VPNs etc.

Do the crashes happen without any VPN running at all?  Or with all proxy settings blanked out?

> Please do it via the Apple logo in the top left

Thanks.  This kind of information is often crucial.  But not (apparently) in this case (at least by itself).  I just tried it and had no trouble.  Today's mozilla-central nightly was running in the foreground.

> OpenH264 Video Codec provided by Cisco Systems, Inc 1.1

This gets downloaded and installed automatically.  But it's probably not involved -- both Stephen and I have it, and don't see crashes.
(Reporter)

Comment 20

3 years ago
Created attachment 8548377 [details]
Crash Log - second mac.

I have downloaded Nightly on a friend's Mac. Created a new location, only put in OpenDNS addresses. Went through the same process as shown in the video to change locations. I was able to reproduce.
(Reporter)

Comment 21

3 years ago
Have done all those steps in comment 12.

>Do the crashes happen without any VPN running at all?  Or with all proxy settings blanked out?

Ok, deleted all locations. Created a new one with zero config changes. Still a crash.



So we are all doing the same process.

OS X Yosemite. 
System Preferences - Network. 
Under combo box 'Locations' click 'Edit Locations', create and name a new location.
Click 'Apply'. No need to add or change any settings in Network.
Load browser.
Making sure browser is in the foreground (check by menu bar is for browser) click on the Apple logo -> 'Locations' and select the new location you created.
>>Do the crashes happen without any VPN running at all?  Or with all proxy settings blanked out?
>
> Ok, deleted all locations. Created a new one with zero config changes. Still a crash.

You didn't answer my question.

Do you have any third-party VPN software?  Do you use any proxy settings (in the Network pref panel)?  Sounds like the answer is "yes" in both cases.  If so, please completely uninstall the VPN software and get rid of the proxy settings, and see if the crashes still happen.

Of these two possibilities, I think it's more likely the third-party VPN software is at fault here.
Another possibility:  Do you have any network-mounted devices when these crashes happen?
Keywords: stackwanted
Whiteboard: [necko-backlog]
You need to log in before you can comment on or make changes to this bug.