Closed Bug 1242888 Opened 8 years ago Closed 1 year ago

Beta version on mac doesn't exit properly

Categories

(Toolkit :: Startup and Profile System, defect, P3)

44 Branch
x86_64
macOS
defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: bobbylon5, Unassigned)

References

Details

Attachments

(9 files)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:44.0) Gecko/20100101 Firefox/44.0
Build ID: 20160120154102

Steps to reproduce:

Get an auto update from firefox and install it.


Actual results:

Firefox reboots i.e. it's supposed to close the old version, finished the install and boot the new version. Instead the old version fails to quit properly.

The new version can still be opened but when trying to quit. That fails to quit also.
No more poppies can be opened and force quit doesn't work.
The bugged out browsers then interrupt everything including the shutdown command.

Meaning the only way to shut the computer down is by doing a hard reset or by removing the power cable.


Expected results:

The first version of firefox should quit completely and correctly.
Stopped shockwave for director add on and unity player add on and build 44.0 Still crashing with the same issue.

Have now disabled all my plugins and will re enable them one by one each update to try and help fix this issue.
Component: Untriaged → Application Update
Product: Firefox → Toolkit
Two updates later and the problem is still occurring.

All my plugins and extensions are now turned off and the issue seems to have evolved.
It now quits the first version of Firefox and 'automatically' boots the update, however the failure to properly exit the first version is still persisting. Which  also knocks on to the second version 'still'.

Meaning the computer needs to be physically disconnected from the power in order to allow the computer to switch off.
Severity: normal → major
OS: Unspecified → Mac OS X
Priority: -- → P1
Hardware: Unspecified → x86_64
Now on version 45.Ob2

Unable to do a bug report as the bug occurs when quitting firefox.
If someone wants to tell me another way to get some information i'll happily do it next update.

As i class this as an annoyance and a critical issue with the beta.
(In reply to bobbylon5 from comment #6)
> Now on version 45.Ob2
> 
> Unable to do a bug report as the bug occurs when quitting firefox.
You are seeing the bug occur when quitting Firefox?
For comment #7
Flags: needinfo?(bobbylon5)
(In reply to Robert Strong [:rstrong] (use needinfo to contact me) from comment #7)
> (In reply to bobbylon5 from comment #6)
> > Now on version 45.Ob2
> > 
> > Unable to do a bug report as the bug occurs when quitting firefox.
> You are seeing the bug occur when quitting Firefox?

The browser quits, but fails to completely quit.
So no crash report is recorded or sent back.

My crash log doesn't show the issue. Probably because i have to unplug the computer to switch it off.
Flags: needinfo?(bobbylon5)
This sounds like the shutdown not completing is preventing the update code from running correctly.

spohl and mstange, would either of you be able to take a look at this?
Component: Application Update → Startup and Profile System
Flags: needinfo?(spohl.mozilla.bugs)
Flags: needinfo?(mstange)
Summary: Beta version on mac keeps bugging out → Beta version on mac doesn't exit properly
This might be a duplicate of bug 1239620. Could you run through the steps in the description of bug 1239620 and let us know if you can reproduce the same issue? Thanks!
Flags: needinfo?(spohl.mozilla.bugs)
Flags: needinfo?(mstange)
Flags: needinfo?(bobbylon5)
Yup the bug has evolved now...


I no longer need to install an update to get it to crash.

Now it seems to crash when the update is ready to be installed and when it's updated.

Tho to confirm the problem itself has also evolved.

It seems to quit the original firefox. Before rebooting it and crashing (application not responding).

Which means i have to go into my app folder and open firefox which brings up a new firefox in the menubar (not in it's usua fixed permanent location as that one has crashed).
Flags: needinfo?(bobbylon5)
(In reply to Robert Strong [:rstrong] (use needinfo to contact me) from comment #10)
> This sounds like the shutdown not completing is preventing the update code
> from running correctly.
> 
> spohl and mstange, would either of you be able to take a look at this?

More like the update is failing and preventing the system from cycling down.

(In reply to Stephen A Pohl [:spohl] from comment #11)
> This might be a duplicate of bug 1239620. Could you run through the steps in
> the description of bug 1239620 and let us know if you can reproduce the same
> issue? Thanks!

It's essentially the same issue, except mine only occurs during updates.

i.e. the browser works fine and behaves normally most of the time. it's only during the receiving of an update to installing an update that issues flare up.

I still have one update to install, but for some reason my browser crashed this time when it received the update (before installation). So the issue seems to be evolving. Which is starting to make me think it might be a virus or something that's latched on to firefox.

However my scans so far have come up negative.
Markus, can you comment on how the reporter could get more information about what's stopping shutdown in this case, as the crashreporter is not coming up?
Flags: needinfo?(mstange)
New piece of information...

I installed an app last night that required my browsers to quit but this was done automatically by the app.
Firefox crashed and went into it's non responding state as outlined in the original report.

With one difference, that i couldn't go into the app folder and open a second browser.

This is quite important because it details that it's not just updates that cause the issue.

Specifically because it may pinpoint the issue to the code that third party software and indeed the updates use to quit the browser.
When Firefox gets into the hanging state, does it still show up in the list of processes in Activity Monitor? If it does, can you please use "Sample Process" (in Activity Monitor, hidden in the gear button or in the View menu) on it and attach the report to this bug?
Flags: needinfo?(mstange) → needinfo?(bobbylon5)
See Also: → 1250901
Nope...   (In reply to Markus Stange [:mstange] from comment #16)
> When Firefox gets into the hanging state, does it still show up in the list
> of processes in Activity Monitor? If it does, can you please use "Sample
> Process" (in Activity Monitor, hidden in the gear button or in the View
> menu) on it and attach the report to this bug?

When the first version quits, the second version now boots automatically. So the activity monitor correctly shows a working version of firefox. However when both versions have been quit. Both show application not responding, the activity monitor shows nothing abnormal and firefox is not there in the open apps.

So no bug report because the bug occurs likely after firefox has quit. And no according to activity monitor the Browser takes no memory or processing power. Yet it still appears in the dock as "Application not responding"

If i had to make an informed guess. I would say that firefox has quit properly but it has failed to tick certain boxes with the OS. Meaning that the os keeps the old version hanging and allows the new version to boot (because it's a new version) but there must be something about why this version hangs when quitting....

As fire fox works normally when no updates are pending.
Flags: needinfo?(bobbylon5)
Not quite what you need but the sample proccess was only available when two versions are open but the first has crashed after an update.

This was compiled immediately after update 45.0.b9

The update installed and the old icon bounced in the dock the arrow below it disappeared. However instead of opening the same icon, that icon keeps the arrow and a new firefox icon appears across the dock. So this status was taken when that occured.

As when the second version is quit. 
Activity monitor shows no firefox.
When in normal (non update) firefox (for me) works normally. Then again i have it ask me when i should install updates. I should at this point note that this setting changed (within the past few weeks) as i had to change it back earlier this week.

For some reason it had changed from asking me when to update, to automatically update.

Something i'm not massively worried about because of the amount of times i've had to reeboot the computer by pulling the plug (so to speak).
Thank you for the comprehensive answer!

Unfortunately I don't know how to proceed from here. We may need to ask for help from somebody at Apple.
Moving to p3 because no activity for at least 24 weeks.
Priority: P1 → P3

In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.

Severity: major → --

Reporter is gone and no one else reproducing -> incomplete

Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: