Memory hog

Heh, it used up so much memory it screwed up your text. [wink]

For some reason I find "Toepassing sluiten" amusing.

I think your program is trying to tell you IE is a sluiten!

It's telling me that I've used too much memory and can't start another application untill I reduce my memory usage, and asks me what application(s) to close. It's Dutch.

Quote:

Original post by Sander It's telling me that I've used too much memory and can't start another application untill I reduce my memory usage, and asks me what application(s) to close. It's Dutch.

Man, that's one crazy language you have there!

Quote:

Original post by Toolmaker Quote: Original post by Sander It's telling me that I've used too much memory and can't start another application untill I reduce my memory usage, and asks me what application(s) to close. It's Dutch. Man, that's one crazy language you have there!

[lol] - funny that coming from another Dutchman!

I want to go back to Holland some day. It is actually quite a nice language, Dutch is.

I don't know what that xml file was doing, but I just opened a similar size one in a second IE window to gamedev, and the memory use remained about 40Mb.

Quote:

Original post by gregs I don't know what that xml file was doing, but I just opened a similar size one in a second IE window to gamedev, and the memory use remained about 40Mb.

And how much did it take before that on a regular page, e.g. the google front page?

did the XML document include a reference to an XSL or a DTD? We have a couple of XML documents here that are quite small, but the XSL transform associated with them is over 72KB alone.

edit: eh, that's not going to get you up to nearly a GB.

IE Google: 15MB
IE with 10MB XML: 170MB

FF Google: 50MB (just opened)
FF with 10MB XML: over 200MB

IE was responsive the entire time while loading. You could scroll to the bottom and watch more pop up. Firefox was unresponsive as soon as the document started to open. It just came up with the Not Responding title when you tried to move it. once it was done loading (memory stopped increasing) it still didn't respond to anything. I had to kill the process to free up the memory.

And someone makes it a browser war...

Quote:

Original post by Puzzler183 And someone makes it a browser war...

You call a simple comparison a browser war?

Quote:

Original post by Puzzler183 And someone makes it a browser war...

IE is a toepassing sluiten!!!

@capn_midnight: Nope. No styles or XSD's.

I wonder why XML viewing in general is such a memory hog. They probabely try to load the entire XML in memory, then convert it into pretty print in memory as well. Surely they can just page in/out the requwsted bits if there are no styles associated with the XML?

@tstrimp

The difference in memory between FF an IE when viewing google is caused by the fact that most of IE is in the kernel, so that memory won't get reported. When I do that under Linux (IE6 under wine) I get nearly identical memory usage between the two of them. I'm surprised by the XML results though.