Bug 3175

Summary:	firefox 7 is unstable
Product:	Mageia	Reporter:	AL13N <alien>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	major
Priority:	Normal	CC:	doktor5000, marja11, n54
Version:	1
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	firefox	CVE:
Status comment:

Description AL13N 2011-10-25 10:42:30 CEST

Description of problem:

Firefox 7 is kind of unstable, v6 was alot better, even though it may leak more memory.

FF7 seems sometimes to hang with 100%CPU (experienced this already 6 times) and sometimes just killing itself (2 times)

Comment 1 Nicolas Vigier 2011-10-25 11:10:26 CEST

Which version of xulrunner packages is installed on your system ?

CC: (none) => boklm

Comment 2 Manuel Hiebel 2011-10-25 11:11:26 CEST

I saw the same thing, but *just* with web pages in Flash.

I think you report this bug upstream at mozilla or adobe. :)

Comment 3 Florian Hubold 2011-10-25 13:22:39 CEST

Firefox 7.0.1 works fine here, also with Flash pages. Not unstable, not freezing, not 100% cpu and not killing itself. Maybe this is due to your plugins or problems with your profile?

FWIW you can check memory usage and possible leaks with about:memory.
And before reporting such things upstream you need to check back with a freshly created profile and upstream tarballs to check if the problem comes from our build.

CC: (none) => doktor5000

Comment 4 Kamil Rytarowski 2011-10-26 03:42:33 CEST

How to reproduce?
Here everything is rock stable.

CC: (none) => krytarowski

Comment 5 AL13N 2011-10-26 20:07:44 CEST

I have no idea how to reproduce, perhaps having multiple cores help to hang it? I only know that i keep open alot of tabs and i never reboot the machine and keep this open 24x7, and since i updated, i got alot of hangs.

Comment 6 Marja Van Waes 2011-12-17 21:04:58 CET

We have FF 8 now, so closing as old.

Status: NEW => RESOLVED
CC: (none) => marja11
Resolution: (none) => OLD

Comment 7 AL13N 2011-12-17 22:41:00 CET

at work with FF8, it seems the memory is slightly better, and i didn't reproduce any similar issues yet, so i'm ok with this.

i note however that FF mem usage(leak) if it's running for a few days, is still taking a huge amount of memory.

after a week, it's still > 2GB, and the about:memory page (which has a "free up  memory" button) doesn't work at all...

best way is to killall -9 firefox and restart with restore all sessions.

Comment 8 Florian Hubold 2011-12-18 13:13:11 CET

Then best recheck with upstream tarballs and report upstream.
And maybe look at comment#1 again ...

Comment 9 AL13N 2011-12-18 22:32:38 CET

likely the latest xulrunner there is in mga1 ...

i'll see about the memory thing later

Comment 10 Florian Hubold 2011-12-19 09:25:23 CET

That was asked because there is a likely possibility that you have many old xulrunner libs installed in paralell.

Comment 11 AL13N 2011-12-19 21:42:43 CET

that is a possibility, allthough it's a pretty new installation (a few months back), but anyways, shouldn't it always use the latest one?

as i said, i kill FF now and then, so i can restore session later
so i assume that the newer xulrunners are being used?

Nicolas Vigier 2014-05-08 18:04:54 CEST

CC: boklm => (none)