Closed Bug 1442235 Opened 8 years ago Closed 8 years ago

[macOS 10.13.3] Firefox is not running but icon in dock bounces every 20 minutes

Categories

(Core :: Widget: Cocoa, defect)

58 Branch
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: david.bagonyi, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36 Steps to reproduce: Installed Firefox 58.0.2, locked it's icon to the dock. Actual results: Firefox is not running, however every 20 minutes (or so) the icon in the dock bounces once and then it stops. I have turned off auto updates in the preferences, but it is still doing the same. To get an idea what it is doing, I did a: `watch -n 0.5 "ps aux | grep [f]irefox"` and logged the results to a file. I found one instance of "/Applications/Firefox.app/Contents/MacOS/firefox --version". Running this manually results in the same behaviour (icon in dock bouncing). Expected results: The icon in the dock should not bounce especially if Firefox is not running.
Hi David, I tested this on Mac OS X 10.13 with FF 58 and FF Nightly 60.0a1(2018-03-06) and I can't reproduce this. Can you please try with FF Nightly? You can download it from here: https://nightly.mozilla.org/ Did you observe this issue only in FF 58 version? Thanks
Component: Untriaged → Widget: Cocoa
Flags: needinfo?(david.bagonyi)
Product: Firefox → Core
Hi Ovidiu, Thank you for getting back to me. I have uninstalled Firefox, and I cannot reproduce this issue using Firefox Nightly. I wonder if it's my antivirus (Sophos) or some other application is trying to keep Firefox up to date. This is a company laptop and interestingly many of my colleagues are experiencing the same. We all have the same antivirus software though. This is unlikely to be an issue with Firefox itself. Happy to have this closed. Thanks, David
Flags: needinfo?(david.bagonyi)
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.