Memory hog software

[AtW]

I start:

Firefox 4.

 

[Spacecadet]

I got off the bandwagon when Firefox 3 came out.

For all the whining that web developers do about internet explorer it would probably help if they could learn to build a web pages which didn't need huge amounts of memory.
Which ever web browser I use these days the browser (chrome at the moment) is usually the second biggest consumer of memory on my laptop, the first being SQL Server
Even Outlooks memory usage is put to shame

 

[stek]

IBM Systems Director - nice but slaughters my 4gb RAM work lappy (I know) I had the green triangle for ages, like hour or so (means starting...) until I got a green circle, fine it all worked. Fukn systray....

But nothing else did so I had to stop it - java.exe taking 2.9GB......

Works great on the AIX Intellistation 9111-285 with 4gb ram, no slow down and starts in a jiffy, so I say it again, the PC architecture (started by IBM!) is shiite...

 

[AtW]

Most webpages should not need much memory - unless they render whole thing into one very large off screenimage and keep it cached in memory for quick scrolling

 

[NickFitz]

For all the whining that web developers do about internet explorer it would probably help if they could learn to build a web pages which didn't need huge amounts of memory.

Ironically, Microsoft is the only browser manufacturer that has ever had to publish official documentation on how to work around acknowledged flaws in its browser's implementation that lead to the leaking of memory when perfectly valid web development techniques are employed. Note that none of the "troublesome [memory leak] patterns you might face" they describe are anything other than artefacts of the way Internet Explorer was implemented, and that they have not affected other browsers in those ways on either Windows or any other platform.

As a bonus, a number of their "workarounds" force one to program in a way that is either counter-intuitive and often counter-productive, as in the need for outside-in DOM construction, or that impedes effective usage of the most important features of the JavaScript programming language.

I merely note in passing the fact that they do not find it necessary to provide such advice for the use of their alternative VBScript browser scripting language. The lack of necessity was not because it is free of such issues (which it isn't as they are mainly down to the underlying COM architecture) as because Microsoft themselves gave up on VBScript-in-the-browser only a year or so after everybody else never even started using it, late last century.

 

[d000hg]

Most webpages should not need much memory - unless they render whole thing into one very large off screenimage and keep it cached in memory for quick scrolling

What do you count as a lot? Don't forget that the back button typically leads to caching a LOT of information and I imagine much is held in RAM rather than loaded from disk for performance reasons.
Having 50 tabs open at once probably doesn't help either.

 

[doodab]

Eclipse can be quite memory intensive.

 

[Sysman]

IBM Systems Director - nice but slaughters my 4gb RAM work lappy (I know) I had the green triangle for ages, like hour or so (means starting...) until I got a green circle, fine it all worked. Fukn systray....

But nothing else did so I had to stop it - java.exe taking 2.9GB......

Works great on the AIX Intellistation 9111-285 with 4gb ram, no slow down and starts in a jiffy, so I say it again, the PC architecture (started by IBM!) is shiite...

What platform was Systems Director developed on though? Stuff developed on one platform often suffers from performance issues when ported to another, and it could be that the IBM developers had nice fancy workstations for SD development.

In that vein, early versions of Mozilla ran reasonably OK on a PC running Linux or Windows, but were dreadful on a VMS box with twice the clock speed and 4 times the memory. However, unlike the other thread where Task Manager and working sets are discussed, VMS had the tools to both monitor and adjust these things for better performance.

 

[Sysman]

Most webpages should not need much memory - unless they render whole thing into one very large off screenimage and keep it cached in memory for quick scrolling

But I've come across an increasing number of sites recently which pull bits of Javascript in from multiple other sites.

I counted a total of 9 external sites referenced by a page I visited yesterday. Who knows what that little lot adds up to...

 

[2BIT]

Eclipse can be quite memory intensive.

I don't think I've ever used an application with 'built in eclipse' written on its splash screen that is not a clunky, unstable, unresponsive and unpredictable piece of crap - certainly lotus notes is a good (or bad) example of this but seems to be pretty prevalent