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

    • Exactly what I was thinking. All of a sudden in span of a month multiple CEO's from scam altman to this clown has had sudden change of heart does not seem organic change lol
    • Microsoft releases Visual Studio Code 1.124 with smarter autonomous AI agents by Paul Hill Microsoft has just released Visual Studio Code 1.124 with a focus on faster agent workflows and improved agent autonomy. Microsoft outlined the following features as the key items in this update: Autopilot: Autopilot, enabled by default, is now smarter to determine when a task is truly done. Background sessions: Quickly send a request in the background and keep composing the next session. Session navigation: Search, jump, and step through agent sessions with the keyboard. Browser history: Revisit and search pages you've already opened in the integrated browser. With VS Code 1.124, Microsoft has enabled Autopilot by default. For those that don’t know, Autopilot is a chat permission level that you can pick to give agents permission to take initiative and act autonomously, without needing explicit user approval for each action. Also related to Autopilot, Microsoft introduced Advanced Autopilot, which changes how Autopilot decides when to keep iterating and when to finish. This helps you get more complete results without manually monitoring loops. This feature works using a small utility model that reads a transcript of the chat and decides when the task is done. Another new feature in 1.124 is the Agents window, which lets you easily explore, iterate on, and review agent sessions across projects and machines. Previously, starting a new agent session meant waiting for it to load before you could compose the next one. With this update, sessions can be requested in the background. This VS Code update also brings session navigation updates to switch between them more quickly. The update also lets you reload or reopen the Agents window so that it no longer loses your layout, so you will land back where you left off. If you use the integrated browser in VS Code, you will notice that it now retains the history of visited pages. Suggestions will now show when typing in the URL bar and can be managed by using Ctrl+H within a browser tab. The browser now also lets you customize the toolbar more; just right-click on the toolbar area to the right of the URL input. Finally, the browser has faster agentic text entry. Another improvement is experimental enterprise-managed Copilot plugin policies that allow admins to centrally control which chat plugins and plugin marketplaces are available to developers. If you have VS Code installed, 1.124 should install automatically, or you'll get a prompt. If you don't have it installed, get it here.
    • Ray-Tracing is the Radeon RX 9070 XT's biggest weakness. The Radeon RX 9070 XT might not be able to match in the GeForce RTX 5070 Ti in ray-tracing, but it can beat the GeForce RTX 5070, which is around the same price.
    • I am also on latest experimental with possible insider flags on and aiming in settings for 26h1.. Also see just this wasted space. I do love "movable" small taskbar though but would love more if it had date next to it now just time.
    • Does not make it more readable for me though. The majority of your screenshot is just pitch black.
  • Recent Achievements

    • First Post
      X-No-file earned a badge
      First Post
    • One Month Later
      johnjacobb40 earned a badge
      One Month Later
    • One Year In
      Primer1st earned a badge
      One Year In
    • Experienced
      JayZJay went up a rank
      Experienced
    • Reacting Well
      Sir_Timbit earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      512
    2. 2
      PsYcHoKiLLa
      220
    3. 3
      +Edouard
      145
    4. 4
      ATLien_0
      87
    5. 5
      Steven P.
      86
  • Tell a friend

    Love Neowin? Tell a friend!