Description of problem: After upgrade of firefox to 60.2 version loading pages could take minutes when we earlier were talking about seconds Version-Release number of selected component (if applicable): 60.2.2 How reproducible: Always Steps to Reproduce: 1.Update firefox to newest version 2.Browse a webpage 3. Tried all the tricks on the Web about speeding up Firefox Quantum to no avail. Finally downloaded the package firefox-52.9.0-1.mga6 and did an "urpmi --downgrade firefox-52.9.0-1.mga6, then the same for firefox-en_US-52.9.0-1.mga6. And all the old speed is back. Version 60 doesn't seem to be a disaster and shouldn't have been included in Mageia yet! I do have a dual core processor only and that could have something to do with it, but everything else works fine.
Whit what sites do you have the behavior you describe? I make a quick test and my regular sites load normal. I have a older processor than you and maybe a slowest connection too. If the site is youtube, in about:config set this to true: dom.webcomponents.customelements.enabled dom.webcomponents.shadowdom.enabled
Every site I tried was far slower than earlier. Didn't test youtube though. I am fine with the old version again and really saw nothing I needed in the new version anyway, Just wish I could block the firefox updates in urpmi as I now will have to remember to untick it during updates. Also tried a clean profile with no extra plugins or extensions. Still very very slow.
(In reply to Dag Nygren from comment #2) > Every site I tried was far slower than earlier. Didn't test youtube though. > I am fine with the old version again and really saw nothing I needed in the > new version anyway, Just wish I could block the firefox updates in urpmi as > I now will have to remember to untick it during updates. > > Also tried a clean profile with no extra plugins or extensions. Still very > very slow. As root add /^firefox/ to /etc/urpmi/skip.list
I find Firefox 60.2.2 on Mageia super fast. Two suggestions. 1. Try clearing the browser cache in case you have some old corrupted data in it. 2. Adjust the FireFox 60 performance parameters. See https://support.mozilla.org/en-US/kb/performance-settings?as=u&utm_source=inproduct for details.
CC: (none) => rihoward1
Thanks for the skip.list tip! And to howard: I tried all that. Creating a new user took care of the cache part and then I did walk through the performance parameters and some more. It got slightly better, but never even close to the old version.
Assigning to all packagers collectively, since there is no registered maintainer for this package. CC'ing some committers. @ Dag Can you please test Firefox 60+ directly from upstream, instead of the Mageia package. If that has the issue, too, then it is likely an upstream issue. If it doesn't, then it is a Mageia packaging issue. .
Assignee: bugsquad => pkg-bugsCC: (none) => lists.jjorge, luigiwalser, marja11, mrambo, rverschelde, thierry.vignaud, tmbKeywords: (none) => NEEDINFO
Thanks Maria! Good suggestion! Did this and downloaded FF 60.0.3. Installed it and the same slowness is back. Took 36 seconds to load this page for example. According to the status field it was evenly spent between Connecting, negotiating TLS and loading data. About 10 secs each. So it is not a MAaeia thing if you are not taking the decision to move to 60+ into account. Anyway when I am now here in total slowness anyway I will try out some more solutions and perhaps try to trace what goes on with wireshark and some strace...
Just tested and changing the number of "Content processes" in performance settings to 1 (!) seems to have brought back most of the speed. I had it set at 2 as I had two cores in the CPU. The "Autotune" settings are a complete disaster... It is still not as fast as the earlier versions but quite close. I should add that I do have 8GB (about 4.5GB free ATM) of RAM and an SSD so everything else than the CPU should be quite Ok. But now I think I could live with this. If someone has a suggestion on bringing back the 10-20% still missing they are very welcome
Load time for this page now 6s. Guess that is Ok? Chrome and konqueror both loads this page in 3s so something is still not quite right. Something in my Mageia or in FF?
Error messages when running firefox. Any indication ? : (firefox:12005): Gtk-WARNING **: Could not load a pixbuf from icon theme. This may indicate that pixbuf loaders or the mime database could not be found. (firefox:12005): Gtk-WARNING **: Theme parsing error: <data>:1:34: Expected ')' in color definition (firefox:12005): Gtk-WARNING **: Theme parsing error: <data>:1:77: Expected ')' in color definition ###!!! [Parent][DispatchAsyncMessage] Error: PClientSourceOp::Msg___delete__ Route error: message sent to unknown actor ID ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
Remove stock FF and reinstalled the Mageia provided one. This page load now takes 9s :-( but the remaining error messages are: (firefox:13779): Gtk-WARNING **: Theme parsing error: <data>:1:34: Expected ')' in color definition (firefox:13779): Gtk-WARNING **: Theme parsing error: <data>:1:77: Expected ')' in color definition ###!!! [Parent][DispatchAsyncMessage] Error: PClientSourceOp::Msg___delete__ Route error: message sent to unknown actor ID ###!!! [Parent][DispatchAsyncMessage] Error: PClientSourceOp::Msg___delete__ Route error: message sent to unknown actor ID
CC: luigiwalser => (none)
(In reply to Dag Nygren from comment #11) Not sure but GTK Warnings maybe is related with this errata https://wiki.mageia.org/en/Mageia_6_Errata#The_breeze_theme_is_not_used_by_default_for_some_KDE_4_and_GTK_applications
Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 6's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/ Best regards, Aurélien Bugsquad Team
CC: (none) => ouaurelienStatus: NEW => RESOLVEDResolution: (none) => OLD