Recommended Posts

You didn't look close enough because I'm not the only one who has this since I just used a script I found......

http://yaku.dk/s/scr...firefox4ftw.png

And you didn't read what he wrote.

Yes - by enabling the menu bar. AFAIK there's no official way to have the Firefox button and the menu off at once though.

The latest nightly seems to break tabs in titlebar implementations... or at least for me, the tabs get pushed down again :(

Same here. Using Minimal 1.0 skin, the tabs moved down a bit and the new tab button is messed up. But that's what you expect when you use nightly.

The latest nightly seems to break tabs in titlebar implementations... or at least for me, the tabs get pushed down again :(

for some reason i have a feeling it has to do with the new code added to make the menu button work in xp and the basic theme, should hopefully be fixed soon

SunSpider results (perfomed on laptop with win7 x64, core 2 duo 2ghz T5800, 3gb ddr2, nvidia 9200LE gpu):

I get a 2.4% speed improvement with SunSpider with ff4b3 compared to ff4b2 as you can see below:

Firefox 4.0 Beta 3:

RESULTS (means and 95% confidence intervals)
--------------------------------------------
Total:                  810.0ms +/- 2.4%
--------------------------------------------

  3d:                   132.8ms +/- 14.0%
    cube:                40.6ms +/- 17.9%
    morph:               39.0ms +/- 45.9%
    raytrace:            53.2ms +/- 10.6%

  access:               112.6ms +/- 5.0%
    binary-trees:        25.2ms +/- 15.4%
    fannkuch:            54.8ms +/- 3.0%
    nbody:               15.2ms +/- 53.8%
    nsieve:              17.4ms +/- 35.2%

  bitops:                34.8ms +/- 14.4%
    3bit-bits-in-byte:    1.2ms +/- 46.3%
    bits-in-byte:        15.2ms +/- 38.1%
    bitwise-and:          3.6ms +/- 52.4%
    nsieve-bits:         14.8ms +/- 11.0%

  controlflow:            9.4ms +/- 27.4%
    recursive:            9.4ms +/- 27.4%

  crypto:                52.8ms +/- 22.4%
    aes:                 27.4ms +/- 5.2%
    md5:                 16.8ms +/- 46.6%
    sha1:                 8.6ms +/- 50.7%

  date:                 106.6ms +/- 9.2%
    format-tofte:        65.0ms +/- 14.8%
    format-xparb:        41.6ms +/- 14.7%

  math:                  71.8ms +/- 15.2%
    cordic:              41.2ms +/- 19.7%
    partial-sums:        21.6ms +/- 26.3%
    spectral-norm:        9.0ms +/- 69.8%

  regexp:                67.6ms +/- 8.8%
    dna:                 67.6ms +/- 8.8%

  string:               221.6ms +/- 11.6%
    base64:              10.8ms +/- 57.2%
    fasta:               33.0ms +/- 26.8%
    tagcloud:            84.2ms +/- 5.7%
    unpack-code:         68.6ms +/- 6.6%
    validate-input:      25.0ms +/- 43.2%

Firefox 4.0 Beta 2:

RESULTS (means and 95% confidence intervals)
--------------------------------------------
Total:                  829.6ms +/- 3.4%
--------------------------------------------

  3d:                   132.2ms +/- 10.6%
    cube:                40.6ms +/- 17.8%
    morph:               40.8ms +/- 36.3%
    raytrace:            50.8ms +/- 19.5%

  access:               113.8ms +/- 14.2%
    binary-trees:        22.2ms +/- 2.5%
    fannkuch:            52.2ms +/- 2.6%
    nbody:               27.6ms +/- 56.6%
    nsieve:              11.8ms +/- 4.7%

  bitops:                34.6ms +/- 11.0%
    3bit-bits-in-byte:    1.0ms +/- 0.0%
    bits-in-byte:        10.6ms +/- 15.7%
    bitwise-and:          2.6ms +/- 64.2%
    nsieve-bits:         20.4ms +/- 3.3%

  controlflow:           11.0ms +/- 33.0%
    recursive:           11.0ms +/- 33.0%

  crypto:                53.0ms +/- 16.7%
    aes:                 29.0ms +/- 10.1%
    md5:                 14.8ms +/- 58.3%
    sha1:                 9.2ms +/- 58.4%

  date:                 107.0ms +/- 4.1%
    format-tofte:        66.0ms +/- 3.3%
    format-xparb:        41.0ms +/- 12.5%

  math:                  67.2ms +/- 8.5%
    cordic:              38.6ms +/- 9.3%
    partial-sums:        19.0ms +/- 0.0%
    spectral-norm:        9.6ms +/- 54.6%

  regexp:                75.0ms +/- 15.0%
    dna:                 75.0ms +/- 15.0%

  string:               235.8ms +/- 3.3%
    base64:               9.0ms +/- 0.0%
    fasta:               28.0ms +/- 4.4%
    tagcloud:            81.4ms +/- 3.2%
    unpack-code:         85.4ms +/- 11.1%
    validate-input:      32.0ms +/- 7.8%

Firefox 3.6.8:

RESULTS (means and 95% confidence intervals)
--------------------------------------------
Total:                 1268.8ms +/- 4.0%
--------------------------------------------

  3d:                   219.6ms +/- 24.1%
    cube:                57.2ms +/- 13.2%
    morph:               65.8ms +/- 14.2%
    raytrace:            96.6ms +/- 45.4%

  access:               190.2ms +/- 5.0%
    binary-trees:        50.2ms +/- 15.5%
    fannkuch:            82.2ms +/- 7.4%
    nbody:               33.2ms +/- 20.4%
    nsieve:              24.6ms +/- 29.2%

  bitops:                60.4ms +/- 17.6%
    3bit-bits-in-byte:    4.0ms +/- 38.1%
    bits-in-byte:        16.0ms +/- 22.7%
    bitwise-and:          4.8ms +/- 53.1%
    nsieve-bits:         35.6ms +/- 39.6%

  controlflow:           53.8ms +/- 24.5%
    recursive:           53.8ms +/- 24.5%

  crypto:                69.0ms +/- 19.7%
    aes:                 36.6ms +/- 20.2%
    md5:                 18.4ms +/- 17.0%
    sha1:                14.0ms +/- 55.8%

  date:                 200.2ms +/- 10.9%
    format-tofte:        99.4ms +/- 9.0%
    format-xparb:       100.8ms +/- 15.3%

  math:                  80.0ms +/- 17.0%
    cordic:              37.4ms +/- 13.2%
    partial-sums:        28.4ms +/- 50.8%
    spectral-norm:       14.2ms +/- 42.6%

  regexp:                68.6ms +/- 12.9%
    dna:                 68.6ms +/- 12.9%

  string:               327.0ms +/- 6.5%
    base64:              18.4ms +/- 36.9%
    fasta:               74.0ms +/- 8.1%
    tagcloud:            90.8ms +/- 6.5%
    unpack-code:        104.2ms +/- 13.4%
    validate-input:      39.6ms +/- 18.8%

With 1 tab open firefox 4b3 uses 59mb ish ram, firefox 4b2 used 82mb ish ram, firefox 3.6.8 uses 60mb ish.

Nags with the beta.

Apparently you can no longer get rid of the annoying tab scroll (who the F wants to scroll through a whole bunch of tabs... they need new UI/usablity designers)

also Who thought it was a good idea to remove the min,max,close widgets.... seriously, that's more annoying than apps that use non standard size/position widgets. again, they need new UI/Usability designers.

When you think FF can't get more stupid, the designers go an prove you wrong again.

Nags with the beta.

Apparently you can no longer get rid of the annoying tab scroll (who the F wants to scroll through a whole bunch of tabs... they need new UI/usablity designers)

also Who thought it was a good idea to remove the min,max,close widgets.... seriously, that's more annoying than apps that use non standard size/position widgets. again, they need new UI/Usability designers.

When you think FF can't get more stupid, the designers go an prove you wrong again.

Hm? Do you mean the min/max/close widgets provided by Windows? They should still be there. :blink:

Firefox 4.0 Beta still has a problem that has changed a bit but not much.

Beta 1 if I launched it from restore with eg 6 tabs it would lag and then half of the time it would crash and I don't have a slow computer.

Beta 2 it would launch but take quite a while and almost crash.

Beta 3 A tiny bit faster again but still around 10-20 seconds.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • 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.
    • "performance issues? what performance issues?!"
    • Microsoft making much needed change to Windows 11, 10 Patch Tuesday security updates by Sayan Sen Recently, Microsoft delivered its latest Defender patches for Windows 11 ISOs. These definitions are released from time to time alongside the general security updates available during Patch Tuesday. Speaking of Defender, the company has now announced another important change that affects how security updates are delivered to enterprise devices running Windows. According to a recent announcement, Microsoft Defender for Endpoint's endpoint detection and response (EDR) updates will no longer be bundled with the monthly Windows security updates or Patch Tuesdays. Instead the company is shifting delivery of these updates to Microsoft Update, bringing EDR servicing in line with several other Microsoft Defender components. If you recall, Microsoft last year moved PowerShell updates to Microsoft Update (MU) as well since it provides automatic updates for Microsoft products and services. Thus the move is intended to allow Microsoft to deliver EDR improvements and security enhancements independently of the OS's regular monthly update cycle; this should enable faster deployment of protection updates without requiring organizations to wait for the next Patch release. For those unfamiliar, Microsoft Defender for Endpoint's EDR capabilities are designed to help organizations detect, investigate, and respond to advanced threats across managed devices. Keeping these components updated is critical for maintaining protection against evolving attack techniques. The rollout has already began for Windows 10 devices in late May 2026 (last month) and Microsoft says it will gradually expand support to Windows 11 and the remaining supported Windows versions over the coming months. The company expects deployment across Windows 10 and Windows 11 to be completed by fall 2026 or around Q3 of this year. Once the transition is complete, EDR updates will be delivered through Microsoft Update using KB5005292, provided the required prerequisite updates have already been installed. Microsoft is also introducing a new Defender Update Service as part of the change. Following installation of the first update, devices will automatically create a new directory located at %ProgramData%\Microsoft\Microsoft Defender\Defender Update. Microsoft notes that restarts may occasionally be necessary in case of "rare" failure scenarios. For most organizations, the tech giant says no action will be required as long as Microsoft Update is already permitted within their update management strategy. Admins who rely on manually deployed update packages, however, will need to adjust their processes to ensure the new Defender update package is included. Microsoft also recommends reviewing internal documentation and notifying helpdesk and security operations teams about the updated delivery mechanism to avoid confusion during the transition. As a prerequisite, the tech giant notes that systems must be running Sense version 10.8798.25857.1000 or later and have one of the following Windows updates (or later) installed: Win11 24H2 KB5062660 (2025-07 Cumulative Update Preview) Win11 23H2 KB5062663 (2025-07 Cumulative Update Preview) Win11 22H2 KB5062663 (2025-07 Cumulative Update Preview) Win10 22H2 KB5062649 (2025-07 Cumulative Update Preview) Win10 1809 KB5063877 (2025-08 Cumulative Update) Server 2019 KB5063877 (2025-08 Cumulative Update) Server 2022 KB5063880 (2025-08 Cumulative Update) Server 2025 KB5063878 (2025-08 Cumulative Update) As always, organizations should verify that their update policies align with the new servicing approach before the broader rollout reaches all supported Windows platforms later this year. In case of major problems, the EDR update can be rolled back to the inbox version stored in %ProgramFiles%\\Windows Defender Advanced Threat Protection (ATP) using: MpCmdRun.exe -RevertMde -Product Edr -ToVersion Inbox For those who have access to the Microsoft 365 Admin Center portal, you can view the message here under ID MC1381119.
  • 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
      248
    3. 3
      Steven P.
      73
    4. 4
      +Edouard
      69
    5. 5
      neufuse
      68
  • Tell a friend

    Love Neowin? Tell a friend!