Funkin Computers

[QueenCanadia]

On want basis are you guy's determining Firefox to be a memory hog.

 

There are many ways a program can use memory. In Firefox it is likely that code is compiled into the program, where IE uses dynamically linked libraries. The key here is that a how much memory a process takes in the windows task manager, may not reflect how much memory it does use.

 

There is also the concept of static loading and dynamic loading. IE may use dynamic loading to only have modules in memory that it immediately needs. This provides a smaller memory footprint, but if the program needs to deal with something that it doesn't currently have loaded, it will have to load that module.

 

Firefox's footprint is likely the result of both of these. Since Firefox is cross-platform, it probably isn't able to use as many of the windows API calls as IE can. This means that it has to implement these calls statically within the program.

Wow, thanks for the thorough explanation. The technical stuff actually makes some sense to me. ;)

[glo]

Maybe it's the Airmiles page.

It loads slow on mine too

[Ravenous itchy]

Wow, thanks for the thorough explanation. The technical stuff actually makes some sense to me. ;)

Don't allow yourself to be drawn in by a somewhat specious post.

[ToadMan]

Dude!! I'm taking a 400 level course in Operating System design. I am currently in the process of implementing a memory manager unit for intel IA-32 architecture. I know a lot about this stuff.

 

I'll admit I have made a number of assumptions, but they are based off my experience and knowledge of operating system internals. I am very confident with them.