Recommended Posts

hmm why would firefox start doing this without updating and any changes to settings/drivers/hardware.

SfZgX.jpg

tried fresh profiles, reinstalling firefox and video drivers. issue is on both 32 and 64 builds and does not occur on other browsers.

incase anyone has this issue, I solved it by removing windows update kb 2670838 that came with IE10.

Azure and DLBI both sped up rendering, you can see as much from tests.

No disrespect Decryptor, and not because your a Mod, but because you seem a really cool guy here in the forums, those are just benchmarkings that in real life matter little. again 1ms faster, oh my god!!!

It's like when they implemented "Load tabs only when selected", that was just to hide the poor performance on Firefox when booting!!!

The feature is nice but it's timing was exactly when people were complaining about start times. And yet on a i5 2500k, with 16GB Ram, and Nvidia 570, with this option off and no tabs to load, Firefox can take 5 seconds to load. Now you might say, "Oh but 5 seconds pass on a blink of an eye", yes but IE9/10 is instant, why can't Firefox be too.

And this is just one example, if sure if I think a little harder, I'll find many more!

Now don't think I'm hatting Firefox, cause I'm not, I want it to be faster on all levels, but Mozilla seems more focused their own OS and mobile stuff than what made them popular on the first place, their DESKTOP BROWSER!!!

I'm not talking about 1ms here or there, I'm talking about things getting 10x faster (One "benchmark" went from 1fps to about 30fps on my Mac with the SVG DLBI stuff) In the best case, it won't help much (because it's already the best case), in the worse case you see a huge improvement.

And on my computer (Which funnily enough is an i5 200k with 16GB of RAM and a GTX 570) Firefox launches in <2 seconds (Nightly is closer to 1s, but it also has less tabs/extensions to load)

Edit: And their mobile stuff is driving desktop enhancements, All the work on off the main thread compositing (for example) is driven by a need to make the mobile UI more responsive, work of which also applies to the desktop.

In Inbound:

JS Engine (related to self-hosted code): https://bugzilla.mozilla.org/show_bug.cgi?id=784293

Bug introduced after Per Window Private Browsing: https://bugzilla.mozilla.org/show_bug.cgi?id=822056 , https://bugzilla.mozilla.org/show_bug.cgi?id=822008 , https://bugzilla.mozilla.org/show_bug.cgi?id=819510

Ion Monkey: https://bugzilla.mozilla.org/show_bug.cgi?id=822042

Image Decoding performance improvement (Snappy): https://bugzilla.mozilla.org/show_bug.cgi?id=811891

Session File read on Background thread (Snappy) - But Backout: https://bugzilla.mozilla.org/show_bug.cgi?id=532150

Compartment JS Inline: https://bugzilla.mozilla.org/show_bug.cgi?id=773911 (Improved CSS performance on Talos)

Imagelib related bug: https://bugzilla.mozilla.org/show_bug.cgi?id=801061 , https://bugzilla.mozilla.org/show_bug.cgi?id=821448

Shutdown Improvement: https://bugzilla.mozilla.org/show_bug.cgi?id=818739 (Snappy P1 bug - vastly improved shutdown on Talos)

JS Engine - Ion Monkey - Array related Performance Improvement: https://bugzilla.mozilla.org/show_bug.cgi?id=821816

Baseline Compiler Preparation: https://bugzilla.mozilla.org/show_bug.cgi?id=821707

Download Panel View Downloads in Library (Landed but Backout): https://bugzilla.mozilla.org/show_bug.cgi?id=675902

JS Engine - ES6 improvement (landed but Backout): https://bugzilla.mozilla.org/show_bug.cgi?id=820180

Ion Monkey - Baseline Compiler related bug: https://bugzilla.mozilla.org/show_bug.cgi?id=820084

Web Audio API related bug: https://bugzilla.mozilla.org/show_bug.cgi?id=820875

JS Engine - Maps: https://bugzilla.mozilla.org/show_bug.cgi?id=817368

Related to Windows 8: https://bugzilla.mozilla.org/show_bug.cgi?id=821679 , https://bugzilla.mozilla.org/show_bug.cgi?id=821454

New YARR related performance win in v8-RegExp: https://bugzilla.mozilla.org/show_bug.cgi?id=808245

(Paris Bindings) WebIDL bug: https://bugzilla.mozilla.org/show_bug.cgi?id=821438 , https://bugzilla.mozilla.org/show_bug.cgi?id=819904 , https://bugzilla.mozilla.org/show_bug.cgi?id=818379 , https://bugzilla.mozilla.org/show_bug.cgi?id=816375 , https://bugzilla.mozilla.org/show_bug.cgi?id=816380 , https://bugzilla.mozilla.org/show_bug.cgi?id=820902

Per Window Private Browsing: https://bugzilla.mozilla.org/show_bug.cgi?id=818732

JS Engine: https://bugzilla.mozilla.org/show_bug.cgi?id=821151 , https://bugzilla.mozilla.org/show_bug.cgi?id=808148

Generational GC - Exact Rooting: https://bugzilla.mozilla.org/show_bug.cgi?id=816779

Ion Monkey: https://bugzilla.mozilla.org/show_bug.cgi?id=814966

Should I post regarding Important bugs landed but backout like currently did or not?

  • Like 2

the more info, the better!

Then I will cover backout information of Important bugs like I do as well since it sometime indicate that they will land sooner in exception cases it is not but majorly it is. So it will be help for users I think.

Thanks Zlip :)

I'm not talking about 1ms here or there, I'm talking about things getting 10x faster (One "benchmark" went from 1fps to about 30fps on my Mac with the SVG DLBI stuff) In the best case, it won't help much (because it's already the best case), in the worse case you see a huge improvement.

But that's the problem, You're assuming in the worst case you'll see huge improvements, when in fact the "laggy UI" is still there, what good is a 1000hp engine is, if the body can't hold more than 100hp without starting to fall apart?

In most i5 and i7 the problem is just hidden because of so much HP, but as soon as you get a less performance CPU and a intregrated GPU you'll notice how laggy Firefox UI is! The body is just top heavy!

And on my computer (Which funnily enough is an i5 200k with 16GB of RAM and a GTX 570) Firefox launches in <2 seconds (Nightly is closer to 1s, but it also has less tabs/extensions to load)

I'm not seeing that in my end, sure if you "open a new window" with Firefox as a process sure, but closing Firefox and re-opening it does take seconds and not 1.

Edit: And their mobile stuff is driving desktop enhancements, All the work on off the main thread compositing (for example) is driven by a need to make the mobile UI more responsive, work of which also applies to the desktop.

I think that decision is wrong and that's why we are where we are.

It should be the Desktop browser the priority.

Seriously how many users does Mozilla mobile have? On the iPhone? There's no Firefox browser (I have to use Opera)... On the Windows Phone? Not that I know about.. On Android? How many? 100k? 200k? A million?

How many Firefox Desktop users? Chrome is eating Firefox share and they are concerned with a very small % of their users on mobile platforms (and like I said before not even that many, actually just one, Android) and then they backport changes to Desktop months latter, if ever?

And using the few resources (man power) they have to build their own mobile OS? Great another dead project from the start! There's already 3 main OS's for mobile, then there's RIM, ex-Palm, etc... There's just no point!

This is Mozilla wanting to be relevant in other areas. But not only are they failing on doing so, they are neglecting their champion!

[update] Firefox Mobile share in %: http://marketshare.h...d=0&qpcustomd=1 0.1%

  • Like 2

Just curious, is this a known bug, or just some glitch on my end?

The generic addon icons are missing:

~snip~

its missing from my plugins page of addon manager as well. I will dig into bugzilla to find bug related to this.

From Inbound:

OS X Flash Crash: https://bugzilla.mozilla.org/show_bug.cgi?id=804606

MemShrink (basically DMD tuning and new memory reporter): https://bugzilla.mozilla.org/show_bug.cgi?id=819817 , https://bugzilla.mozilla.org/show_bug.cgi?id=821577 , https://bugzilla.mozilla.org/show_bug.cgi?id=818060

Canvas 2D Spec bug: https://bugzilla.mozilla.org/show_bug.cgi?id=803124

unprefixing of Gradients in FF Theme: https://bugzilla.mozilla.org/show_bug.cgi?id=821968 , https://bugzilla.mozilla.org/show_bug.cgi?id=821971

(Kind of Refactoring of code going on - Backout also) ImageLib bugs: https://bugzilla.mozilla.org/show_bug.cgi?id=815471 , https://bugzilla.mozilla.org/show_bug.cgi?id=816362 , https://bugzilla.mozilla.org/show_bug.cgi?id=816374 , https://bugzilla.mozilla.org/show_bug.cgi?id=821023

Crash fix in DOM: https://bugzilla.mozilla.org/show_bug.cgi?id=820373

Cleanup in Encoding Menu (Show only standard encoding): https://bugzilla.mozilla.org/show_bug.cgi?id=805374

DOM: https://bugzilla.mozilla.org/show_bug.cgi?id=818281

Crash in Layout: https://bugzilla.mozilla.org/show_bug.cgi?id=696640

Top Crash in Layers: https://bugzilla.mozilla.org/show_bug.cgi?id=813024

SVG Invalidation in DLBI: https://bugzilla.mozilla.org/show_bug.cgi?id=802628

Crash: https://bugzilla.mozilla.org/show_bug.cgi?id=822040

SVG Performance regression when HWA is ON: https://bugzilla.mozilla.org/show_bug.cgi?id=820061

CSS Background mess up when HWA is OFF: https://bugzilla.mozilla.org/show_bug.cgi?id=819915

New Downloads View in Library (Relanded): https://bugzilla.mozilla.org/show_bug.cgi?id=675902

Related to XPCOM cleanup: https://bugzilla.mozilla.org/show_bug.cgi?id=820182

Paris Bindings (WebIDL): https://bugzilla.mozilla.org/show_bug.cgi?id=821593

  • Like 3

Posting only two bug currently because these are SUPER AMAZING::

https://bugzilla.moz...g.cgi?id=815748

https://bugzilla.moz...g.cgi?id=799315

It is to enable system wide codec to support MP3 and H.264 codecs for Windows Vista+, it is preferred off due to few reasons.

To enable it, go to about:config and toggle this to true:

media.windows-media-foundation.enabled

Remember it is in Inbound which is not merged to mozilla-central yet so try it after one or two days.

  • Like 2

What I like the most about using Nightly builds is that you never know what fixes are included untill hours after you update.

I think we can track the builds from TBPL and see which Nightly build cooking and then estimate with update release time. Means build take times. So overall not very surprise process for me at least.

I think we can track the builds from TBPL and see which Nightly build cooking and then estimate with update release time. Means build take times. So overall not very surprise process for me at least.

This is true but there was a time when the builds thread was updated as it should be. I long for those days. Without the updates all they need to do is post the change log for the build.

This is true but there was a time when the builds thread was updated as it should be. I long for those days. Without the updates all they need to do is post the change log for the build.

Agree!!!!

what you should do is just copy what Arjen or Peter6 Nightly Threads ( Bugs etc ) an Paste it into the forum, that way i wouldnt have to visit Mozillazine forum anymore

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Posts

    • Dell, HP PCs ran into endless reboot, BitLocker recovery loops but Windows 11 isn't to blame by Sayan Sen Last month Neowin reported on a major issue on Dell systems wherein a bug in its official support tool was leading to endless blue screen of death (BSOD) and restarts. Following our report, Dell officially acknowledged its SupportAssist-related crash issue, confirming that the culprit is not Microsoft's operating system but rather a faulty version of its own remediation software. In a newly published support advisory, Dell stated that version 5.5.16.0 of Dell SupportAssist Remediation and Alienware SupportAssist Remediation can trigger blue screen errors and unexpected system restarts. The company notes that the problematic component operates independently of the main SupportAssist application, meaning users should not remove the primary SupportAssist software when troubleshooting the issue. According to Dell, the crashes are linked specifically to the SupportAssist Remediation service, which is bundled with SupportAssist OS Recovery Tools, and as such it has since released an updated version, 5.5.16.1, which is said to resolve the problem. Affected users are advised to first verify whether version 5.5.16.0 is installed by checking the Installed Apps section in Windows Settings. If so, Dell recommends updating SupportAssist OS Recovery Tools through either SupportAssist's "Update Software" feature or Dell Command Update. Dell also advises users to back up important data before performing the update and to ensure systems remain connected to power throughout the installation process. If you are still having issues though make sure to report to the Dell support forum. As it turns out though Dell is not the only PC maker currently dealing with update-related headaches as HP is also facing a separate but probably equally frustrating issue involving recent Windows Secure Boot updates that were released with recent Windows 11 Patch Tuesdays. Similar to Dell, HP also put up its own support article where it explains the issue. The company says that affected devices could hit a brick wall when booting as they run into a BitLocker recovery loop after the April 2026 updates. The problem appears to affect systems wherein the new UEFI Secure Boot CA 2023 certificates fail to apply properly. As such affected users will find themselves entering their recovery key over and over again despite the system otherwise functioning normally. HP says such PCs should be updated to the latest available BIOS version and configured with the necessary Secure Boot certificates before installing Microsoft's Windows 11 Patch Tuesday updates. Systems that are already experiencing the problem may require BIOS configuration changes to restore normal boot behavior. Admins can find information regarding that in the support article here on HP's official website.
    • Getting further away from the artistic study of mental disease that was the first game... (which never needed any sequels to begin with) But I get it, a company has to make money. And the second was at least visually impressive, if not in any other way.
    • If its the devs fault you would think Unreal would help M$ take full advantage of Unreal and work with them to fix the performance issues. Otherwise they are catching unwarranted bad press.
    • Thanks for the advice guys, I'll give my current GPU a clean and then run the benchmarks to see how similar it is. Hopefully a bit of a clean-out will help it last a bit longer.
    • Pretty sure those will still be in this game. The series' well-explored psychosis themes will return as well.
  • Recent Achievements

    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      493
    2. 2
      PsYcHoKiLLa
      246
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      69
    5. 5
      neufuse
      68
  • Tell a friend

    Love Neowin? Tell a friend!