latest updates of Aurora is causing system to hang

RESOLVED INCOMPLETE

Status

()

Firefox
General
RESOLVED INCOMPLETE
6 years ago
6 years ago

People

(Reporter: Landis Reed, Unassigned)

Tracking

({hang})

11 Branch
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
User Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0a2) Gecko/20120103 Firefox/11.0a2
Build ID: 20120103042005

Steps to reproduce:

the last few days updates on All my openSuSE systems from 11.2, 11.3, 11.4 and 12.1 running KDE hang. 


Actual results:

the last few days updates on All my openSuSE systems from 11.2, 11.3, 11.4 and 12.1 running KDE hang. On the openSuSE 11.4 system (an IBM ThinkCentre) I KNOW it hangs because it's in my kitchen and the processor fan speeds up when the system is doing something. Well that system is doing nothing and the fan is non-stop fast. When I activate the screen it's at Aurora and I Ctrl+Esc and firefox is pegged. It's not been doing anything since last restart for update. On my systems that I use more often including my may coding workstation, I also have slowed system response Due Entirely to Firefox.. If I kill -firefox all is good. 


Expected results:

Nothing, if it's not being used, nothing. It should NOT be using 800 MB of ram to set there after restart from updates. I should Not be slowing down Every system I have.
(Reporter)

Comment 1

6 years ago
just to be clear, this has only gotten unbearable in the last 2 or 3 updates. It's been slow for a long time, but not hanging every system it's on until the last few days.
(Reporter)

Comment 2

6 years ago
I also notice, on the systems that 'aren't doing anything' it is the update manager dialog window that is up on the screen. It effects the mouse, window manager, processor, almost everything.

I've chosen to Not be notified (have firefox automatically check for updates) some where updating automatically too.. Stop both. chose to 'do not check' for now.. 

Landis.

Comment 3

6 years ago
Does the issue still occur if you start Firefox in Safe Mode? http://support.mozilla.com/en-US/kb/Safe+Mode

How about with a new, empty profile? http://support.mozilla.com/en-US/kb/Basic%20Troubleshooting#w_8-make-a-new-profile
Component: General → Untriaged
Keywords: hang
QA Contact: general → untriaged
(Reporter)

Comment 4

6 years ago
i'm checking.. I've started it on the IBM ThinkCentre running openSuSE 11.4. I have to wait for it (Aurora) to check for updates to see if it still hangs system.. 23:20 -5 gmt

Landis
Component: Untriaged → General
(Reporter)

Comment 5

6 years ago
i am also going to start a 'add-ons disabled' version on the Dell Optiplex running openSuSE 11.3 to see if it's hardware.

Landis.
(Reporter)

Comment 6

6 years ago
(In reply to Tim (fmdeveloper) from comment #3)
> Does the issue still occur if you start Firefox in Safe Mode?
> http://support.mozilla.com/en-US/kb/Safe+Mode
> 
> How about with a new, empty profile?
> http://support.mozilla.com/en-US/kb/Basic%20Troubleshooting#w_8-make-a-new-
> profile

I am starting in safe mode on on system and 'add-ons' disabled on a basic install on another, both running releases 11.3 and 11.4 openSuSE

Landis.
(Reporter)

Comment 7

6 years ago
again, i have 2 systems running test, one openSuSE 11.2 the other 11.4.
the 11.2 system has barebones install from nightly, Aurora and has done it's check for updates, and was waiting for me to install and restart. top shows no firefox over process.. 

Waiting on the openSuSE 11.4, Aurora started with add-ons (extensions) disabled to 'check' for update.
(Reporter)

Comment 8

6 years ago
what a dumb ass i am... i had the 11.4 system set to 'never check' and not check, but ask.

Landis.

Comment 9

6 years ago
Hello Landis, have you tried Firefox-12.0a2? I don`t experience this problem with that version under openSUSE 12.1, Gnome 3.2.2.

Updated

6 years ago
QA Contact: untriaged → general

Comment 10

6 years ago
lacks response
Status: UNCONFIRMED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.