Posts with tag "Internet Explorer 8"

Firefox is raping my memory

I realize that just about everyone and their brother in the tech work is all infatuated with Firefox but why this browser gets such a walk when it comes to memory problems is beyond me. I had originally switched to Chrome when it came out because I wasn’t happy with the beta of IE8 (still not) and I never really liked Firefox but recently I decided to give the new beta of Firefox another try.

Even though initially it used more memory than Chrome I continued using through several beta updates even though I did experience problems with it. That was until yesterday though when I finally had enough of the browser deciding that my memory (2Gig) was a three course meal. Within a few seconds of starting up Firefox after rebooting my system this is what Task Manager informed me that Firefox (with 3 tabs loading and no plugins installed) was using this amount of memory

Firefox memory seconds after starting up

After waiting a little bit longer to see if the remaining two tabs would finally load this is what Task Manager informed me Firefox’s memory usage was

Firefox memory before closing it out with Task Manager

Sorry but that just isn’t acceptable.

Related articles by Zemanta

Reblog this post [with Zemanta]

IE 8 Intranet Compatibility – Making A Mountain Out Of A Molehill

Making a mountain out of a molehill Why is it that when the subject of Microsoft or Internet Explorer comes up in conversation any business sense goes right out the window especially within the tech industry. A prime example of this is the stupid fuss being made over the fact that Microsoft has decided to enable IE 8’s Compatibility Mode in the case of Intranets. Now, just to clarify – this is for cases of the IE 8 browser being used on internal company networks which is commonly referred to as intranets. This is not the case when the browser is being used to browse the Internet.

This change in the default settings for IE 8 (from Beta 2 onward) prompted a attention grabbing post headline from Matt Craven over at the Blog Herald where he proclaim Microsoft breaks standards compatibility promise with IE8 Beta 2. While Matt was framing his post around an equally specious post by Harkon Lie the CTO of Opera in The Register Matt used this as yet another reason why Firefox was his browser of choice.

The fact that Harkon Lie could only point to this; and the fact that IE 8 couldn’t pass the Acid 3 Web Standards test (which Firefox has chosen not to try and pass either by the way), as a reason against using the browser is utterly ridiculous. One only has to use the very points raised by Harkon in his post to understand the reasoning for the change. As he points out

The PC market can be split into two segments — the enterprise market and the home market. The enterprise market accounts for around 60 per cent of all PCs sold, while the home market accounts for the remaining 40 per cent. Within enterprises, intranets are used for all sorts of things and account for, perhaps, 80 per cent of all page views. Thus, intranets account for about half of all page views on PCs!

80% of all page views.

Now, considering that these corporations probably have millions of dollars invested in web applications that run on these intranets can you imagine the uproar if they all started breaking. All because Microsoft decided not to enforced this Compatibility Mode right across the board for intranets. Many of these intranets are using a myriad of ActiveX components and custom coding that are not web standards compliant. To expect them to either re-code everything or to have IT departments waste money and resources on something that Microsoft can solve with one simple adjustment is stupid.

Internet Explorer 8 is going to have a hard enough time as it is when it officially launches. Silliness like this is nothing but a case of misdirection and FUD from a company that is a minor player in the browser field. Our time would be better spent on using the browser during its beta releases and helping web developers get ready for the change that is coming as IE8 becomes web standards compliant. Big deal if it isn’t intranet compliant.

Related articles by Zemanta

IE8 Not Ready For Prime Time Unless You Like Self-Abuse

Windows Internet Explorer 

Image via Wikipedia


As anyone who reads this blog regularly will know I like using Internet Explorer and am not a fan of Firefox. Additionally I have tried Opera through many of its versions but never stuck with it for whatever reasons. Where Safari is concerned I have tried it since the first version for Windows was made available and if it wasn’t for one bad bug I would probably end up using it over Internet Explorer. So being a regular user of IE I obviously was interested when they announced that the second beta of the browser was available for download and grabbed myself a copy.

I also know very well that this release was still considered a beta and as such isn’t meant for anything more than finding the bugs on the road to going gold. So with that understanding I installed IE yesterday and proceeded with my daily routine and waited to see when and how IE would fall down – if it did. As far as any of the settings for it I left everything at the defaults that it would have imported from my previous IE 7 install which will be the case with your average user who downloads and installs it. I won’t bother going into any great details about the changes or supposed improvements because that has already been well covered by Ed Bott which you can read about on his ZDNet blog.

What follows here instead is some of the problems that I have experienced in using this release. Some are ones that should be expected from Microsoft’s move the bring IE right up to current web standards and others are those weird and wonderful ones that come from using beta software. As a startup reference point the following graphic displays the resources begin used by a default install of IE 8 Beta 2 with 3 open tabs:

IE 8 Startup with 3 open tabs (Task Manager)

Now being the typical blogger that I am the first site I checked out in the browser was WinExtra which played pretty well with the only exception being the Lijit search widget. For some reason in IE it insists that the button goes under the text entry field but in IE7, Firefox and Safari it displays as it should right beside the text area

Lijit Search Widget

One other thing that I found wasn’t working in the way the plugin company or the blog owners intended it to is the Snap plugin. On blogs that have it enabled IE 8 users will see the following example when visiting

Snap plugin

Then whenever they hover a Snap linked item they will see the following

Snap Plugin

The displayed popup should be displayed right of off the linked text rather than the top left hand corner. While I am sure that most people won’t be concerned since the Snap plugin isn’t one of the more favoured plugins by blog visitors.

The one other big problem I had was with the Share This option link which allows visitors to share the selected post with their various networks like Digg. While it displays okay within the posts

Share This Link 

And it should show like this – as it does in Firefox

Share This Firefox

What we get on WinExtra when we click the link is this instead

Share This Extended IE8 WinExtra

And at this point the browser locks and when you look in Task Manager you see it chewing through resources where it starts from the base amount shown in the first graphic of the post and continues to climb until you kill the IE process in Task Manager

IE8 WinExtra Share This Extended

Restarting I figured I would try again using another site to test only to find that when I clicked on the Share This link the page went white

Share This New Tab Mashable

And once again looking in Task Manager we can see it chewing through the resources in the same way as it had done in the other test

Mashable Share This Extended

At this point I figure I have had enough fun and call it quits on any more checking out of Internet Explorer 8 because quite obviously – or at least from my experience – this browser isn’t ready for any real serious use. What I have to find out now is can this be rolled back to IE 7 or am I going to be really pissed at myself when I find out I’m stuck until the next release.

Related articles by Zemanta