Recommended Posts

I don't understand why Firefox memory usage is so low compared to the rest. Since the 0.x beta days they had a huge memory leak. However they never acknowledged it as a memory leak: they called it a 'feature' in that it saves the browsing sessions of closed tabs and previous pages.

Hasn't been an issue for good bit of time now (fixed in.. v4? I forget), unless you have an addon that's misbehaving. Last few versions, as least with the 20 or so addons that I'm using, Firefox has been quite good with memory usage, usually winding up using more or less half the memory of Chromium with similar addons.

Where did I say anything about low marketshare? I said high marketshare (or no competition) tends to lead to laziness. When IE6 was released there really wasn't any competition. Opera was around but it wasn't free, Firefox wasn't around till 2004, Netscape was as good as dead, Chrome didn't exist, and Safari was released in 2003 on OS X. So Microsoft had no incentive to further develop their browser because there wasn't any other product to compete with, and hence no reason for them to spend money developing it further. Opera was also a paid app until version 10 so their incentive to develop came from their need for money. Nowadays the desktop browser may be free but they earn a good deal of money from licensing (Wii browser is powered by Opera, HTC used to use their browser as default etc).

Dude, I was not arguing with you... I was just saying.

Nothing is wrong. In Windows 8 RTM 64-bit, Internet Explorer always shows up as iexplore.exe (without *32, unlike other software).

Go ahead and launch it from Program Files (x86) and see for yourself.

Also try this: launch IE from the taskbar and check out your user agent as I suggested before.

That's my point. I did check, and my clean install is running IE64, and when I run IE32 it shows that it's 32-bit in the Task Manager.

When I attempt to Pin IE64 to the taskbar it notes that it is already pinned in the context menu. IE32 however notes that it is available to pin to the taskbar.

I just don't want you to have invalid results since I'd like to see a good comparison review. :)

I just reinstalled Windows 8 on the test system just for you. Clean installation (not upgrade). Didn't install anything. Didn't change anything.

Desktop's IE10 uses 32-bit tabs.

Metro's IE10 uses 64-bit tabs.

It even appears in the user agent:

32-bit tab user agent: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.2; WOW64; Trident/6.0)

64-bit tab user agent: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.2; Win64; x64; Trident/6.0)

See for yourself on http://www.whatismybrowser.com and http://whatsmyuseragent.com.

That is odd, to me... because my clean install uses 64 bit all around.

[edit]

Not criticizing in any way, just actually wondering why the difference.

They should look at the html5test.com and try to get at least 400 score on there. It seem like it's the standard use for browser scoring in HTML5.

Is Microsoft going to release IE10 for Windows 7? If not, can we still take them (Microsoft) seriously? Really, they break the internet with their different IE versions.

Yes, they are suppose to but I imagine it will be sometimes after October 26, when they release Windows 8 to the general public.

This article explains why the browser is always 64bit, but the content is 32bit (desktop) and 64bit (metro). http://blogs.msdn.com/b/ieinternals/archive/2012/03/23/understanding-ie10-enhanced-protected-mode-network-security-addons-cookies-metro-desktop.aspx

You can also force 64bit everywhere by enabling Enhanced Protection Mode under the Advanced tab in Internet Options.

For IE10, we?ve changed IE such that Manager Processes always run as 64bit processes when running on a 64bit processor running a 64bit version of Windows. This improves security among other things. We do not expect that this change will meaningfully impact compatibility, because the Manager Process is designed not to run 3rd party content, and thus there?s little opportunity for anyone to take a dependency upon the Frame Process? bitness. In support of this change, the various registry points that point to Internet Explorer have been updated to point to C:\Program Files\Internet Explorer\iexplore.exe. If you manually invoke C:\Program Files (x86)\Internet Explorer\iexplore.exe, that 32bit process will simply launch the 64bit version of iexplore.exe (with the appropriate command line parameters) before exiting.

For the Content Processes, the story is a little more complicated. In the Metro-style experience of Internet Explorer, all Content Processes will run at 64bit (on Win64), which means that they benefit from the improved security provided in 64bit. The compatibility impact is minimal because Metro-style IE does not load any browser add-ons (Toolbars, BHOs, and non-browser-platform COM objects like MIME Handlers, URLMon Protocol Handlers, MIME Filters, ActiveX controls, etc). Back in IE9, running in 64bit mode meant that JavaScript was not JIT-compiled, but for IE10, the JIT compiler was enhanced to work for both 32bit and 64bit tabs, providing great performance in both. Additionally, many major browser add-ons like Flash, Silverlight, and Java are now available in 64bit versions.

In Internet Explorer on the Desktop, by default, Content Processes remain at 32bit by default for compatibility with 32bit ActiveX controls, Toolbars, BHOs, etc. Even when you directly launch the 64bit iexplore.exe executable, you will still have a 64bit Manager Process that hosts only 32bit Content Processes. If you want to enable 64bit Content Processes for the Desktop, you must tick the Enable Enhanced Protected Mode option in the Security section of Internet Explorer?s Tools > Internet Options > Advanced tab. When this option is enabled, all Content Processes that are running in Protected Mode (e.g. Internet Zone and Restricted Zone, by default) will begin to use 64bit Content Processes.

http://html5test.com/

Your browser scores

319

and 6 bonus points

out of a total of 500 points

You are using Internet Explorer 10.0 on Windows 8

---------------------------------------------------------------------------------------------

Your browser scores

345

and 9 bonus points

out of a total of 500 points

You are using Firefox 14.0.1 on Windows 8

So, which browser is better? :p

http://html5test.com/ Your browser scores 319 and 6 bonus points out of a total of 500 points You are using Internet Explorer 10.0 on Windows 8 --------------------------------------------------------------------------------------------- Your browser scores 345 and 9 bonus points out of a total of 500 points You are using Firefox 14.0.1 on Windows 8 So, which browser is better? :p

The answer to that is clear...

your browser scores

437

AND 13 BONUS POINTS

out of a total of 500 points

You are using Chrome 21 on Windows 8

The answer to that is clear...

Thanx for that FFM. But I will stick to my firefox, for now.

For the upteenth time, the so-called "HTML 5 Test" doesn't actually measure anything but just asks if the feature is implemented. Quantity over quality...

I understand that. Someone was asking for the html5 test and I obliged. My self, I could care less about benchmarks on anything. If I did, I would be running an i7-3770 Processor. But I'm not. I'm running an AMD 970 BE. But then, I prefer AMD. Will be getting the FX-8150 BE in a few days.

This article explains why the browser is always 64bit, but the content is 32bit (desktop) and 64bit (metro). http://blogs.msdn.co...ro-desktop.aspx

You can also force 64bit everywhere by enabling Enhanced Protection Mode under the Advanced tab in Internet Options.

That's exactly correct. That would explain why they are showing the browser info as WOW64. So in a way both sides were correct here, just about different aspects of how it worked.

ACID3 test be came the standard for how good the browser was 5 years ago and now html5test is becoming the new ACID3 test standard that web developers are using. The whole point of it is to show your browser is on par with others and web developers see that as to which browser I'm going to but more time into.

It'd be nice it there was also a practical test - like a UI responsive test during loading / panning / zooming etc. At this point, the responsiveness and fluidity of the browsers is becoming more important to the actual browsing experience than than the raw rendering / processing prowess. Of course it's doubly important IE 10 does well there, given that it'll be powering a large number of the new style UI applications. (And most of the Microsoft made Win8 applications are HTML & CSS apps using the IE 10 engine)

(Though if they can keep beefing up those Canvas / Animation scores I'm not complaining :p)

It'd be nice it there was also a practical test - like a UI responsive test during loading / panning / zooming etc. At this point, the responsiveness and fluidity of the browsers is becoming more important to the actual browsing experience than than the raw rendering / processing prowess. Of course it's doubly important IE 10 does well there, given that it's powering a large majority of the new style UI applications

(Though if they can keep beefing up those Canvas / Animation scores I'm not complaining :p)

For me, the litmus test is ease of use, and I'm sorry Microsoft, but sticking the refresh button on the other side of the address bar, away from the navigation buttons, GETS UP MY NOSE! GRR! :p

Also, Tracking Protection Lists are rubbish and don't block YouTube ads at ALL...

For me, the litmus test is ease of use, and I'm sorry Microsoft, but sticking the refresh button on the other side of the address bar, away from the navigation buttons, GETS UP MY NOSE! GRR! :p

Also, Tracking Protection Lists are rubbish and don't block YouTube ads at ALL...

You do know you can change that right? Just right click on the refresh button and say to show before address bar.

Here you go: http://www.neowin.ne...op-in-windows-8

See, I told you so. :D

Hence why I said we were both correct. It is a 64-bit process, but using 32-bit tabs for compatibility. I find that odd to be honest...but can understand why they are doing it that way...

IMO they need to update Silverlight then, since I prefer using IE for Netflix, and would like to have it be a 64-bit process. Otherwise why did they spend time developing the 64-bit version of Silverlight?

This topic is now closed to further replies.
  • Posts

    • The machines are starting to fight back any way they can.
    • No news articles about the Arch Linux repo being majorly infected with malware?!?
    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
  • Recent Achievements

    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      70
  • Tell a friend

    Love Neowin? Tell a friend!