Bug 18699 - firefox-45.2 and firefox-38.8 hogs 100% CPU time
Summary: firefox-45.2 and firefox-38.8 hogs 100% CPU time
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO, UPSTREAM
Depends on:
Blocks:
 
Reported: 2016-06-13 19:27 CEST by Bjarne Thomsen
Modified: 2017-01-07 10:47 CET (History)
6 users (show)

See Also:
Source RPM: firefox-45.2.0-1.mga5
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Bjarne Thomsen 2016-06-13 19:27:04 CEST 
Description of problem:
firefox-45.2 was suddenly very slow today.
Then I discovered that it was hugging 100% CPU-time.
I have now downgraded to firefox-38.8, but the situation is the same.
This seem to indicate another component.
I am updating updates_testing on a daily basis.
I am now using the chromium-browser.

Any ideas?

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
Comment 1 Bjarne Thomsen 2016-06-15 23:32:59 CEST 
The chromium-browser is now also hanging! But it gave an ups, something
about webGL. What is this js 3D rendering. Has something been updated
relating to webGL? It should not be possible to hang browser completely.
How can a user know what is going on?
Comment 2 Marja Van Waes 2016-06-16 15:35:48 CEST 
(In reply to Bjarne Thomsen from comment #1)
> The chromium-browser is now also hanging! But it gave an ups, something
> about webGL. What is this js 3D rendering. Has something been updated
> relating to webGL? It should not be possible to hang browser completely.
> How can a user know what is going on?

No idea :-)

Maybe there's something in the journals?

Please attach journalctl.txt that is the result of running, as root,

   journalctl -ab > journalctl.txt

Of course: run it after first reproducing the problems with firefox and then (after closing or killing firefox) with chromium-browser.

Keywords: (none) => NEEDINFO
CC: (none) => doktor5000, lists.jjorge, mageia, marja11, pkg-bugs, thierry.vignaud

Comment 3 Bjarne Thomsen 2016-06-16 18:21:49 CEST 
I know what page is causing the problem. It is the national Danish radio and
TV homepage: www.dr.dk
But it used to work without any problems.
I have used www.dr.dk as startup page for years.
Comment 4 Thierry Vignaud 2016-06-16 18:36:03 CEST 
It used to be but maybe the website was updated with some more heavy js stuff and the like...
Comment 5 Thierry Vignaud 2016-06-16 18:37:52 CEST 
eg, on FC23, using firefox 47, opening one tag on this site does makes ff eating quite a lot of CPU. On a powerfull laptop.
Comment 6 Thierry Vignaud 2016-06-16 18:38:06 CEST 
You can report that upstream on mozilla.org
Marja Van Waes 2016-06-16 20:11:51 CEST

Keywords: NEEDINFO => UPSTREAM

Comment 7 Marja Van Waes 2016-11-23 08:41:34 CET 
(In reply to Thierry Vignaud from comment #6)
> You can report that upstream on mozilla.org

@ Bjarne

Is this bug still valid with firefox-45.5.0-1.mga5 ?

If yes, and you reported it upstream, then please give the link to the upstream report.

Keywords: (none) => NEEDINFO
Source RPM: (none) => firefox-45.2.0-1.mga5

Comment 8 Marja Van Waes 2017-01-07 10:47:32 CET 
(In reply to Marja van Waes from comment #7)
> (In reply to Thierry Vignaud from comment #6)
> > You can report that upstream on mozilla.org
> 
> @ Bjarne
> 
> Is this bug still valid with firefox-45.5.0-1.mga5 ?
> 
> If yes, and you reported it upstream, then please give the link to the
> upstream report.

No reply, closing as OLD

Feel free to reopen while providing that link :-)

Status: NEW => RESOLVED
Resolution: (none) => OLD
Note You need to log in before you can comment on or make changes to this bug.