This is CRAZY! XML, major problems

[Senteaf]

I can't stand it!!!!


I tried to open an .XML file (less than 100mb) on firefox and chrome;
firefox
I opened it in the browser and waited(only this tab open!). 3 minutes later, the goddamn process was using 1.5GB of RAM!!!!!!!!!!!!!
And I have 1.87GB usable RAM, so it started not responding... cursor froze [...].I was lucky enough to get task manager to end this process.
THE PROCESS IS DEAD.
chrome
I was monitoring the memory usage of chrome while trying to open the .XML.
I was waiting. surprisingly on chrome, as opposed to firefox, it worked(or I thought it did) by showing me the first few lines of the "huge" XML files.
I thought "maybe it would work now" but it got stuck and I said I had enough, and I ended the process.

SO, I can't open a ****ing .XML file!!!!!!
WHAT THE HELL?!


few other major problems:
1. sometimes it take more than 5 seconds to open paint - what?!
2. when I click CTRL + C(on any program) to save something, at best it would take 3 seconds to open the "save as" window. However, the next time I try, it is fine and opens smoothly(I guess I can call it smooth)
3. Sometimes when I "hover" with my mouse over the icons on windows task bar to see previews, it takes too long. sometimes my cursor freezes for 1-2 seconds before showing a preview.


Anyone? help? please!

 

[Mellon Head]

Given your clock speed, 5 seconds to open Paint isn't all that surprising. I wouldn't call that an excessive amount of time, really. The same with the saving and the hovering.

As far as the XML stuff goes, if you're doing XML editing, try a program like Notepad++. It works better and has a smaller footprint than most browsers. I don't know why it would take minutes to load an XML file in a browser, unless the file was huge, and yours wasn't.

Have you checked to see how many processes and services are running in the background? Having something that's resource hungry running while you're trying to do any work can really slow you down.

 

[Senteaf]

What's wrong with my clock speed?

The XML is exactly 77 MB!
I can't open it in any browser, I still don't understand why!
Only the browsers were running while I tried to open the XML file.

 

[Mellon Head]

There's nothing wrong with your clock speed. What I was saying is that at your clock speed, it isn't unrealistic for a program to take a few seconds to load, especially if you have a laptop with a spinning drive, and some processes running in the background. A computer with a faster clock speed, or with an SSD may load it faster. It depends on a lot of things, but I don't think that the wait times that you have are unreasonable (except for the browser - something not right there.)

And I stand corrected, your 77 MB XML file is huge, and that is a lot of data for a browser to have to parse and display. Is there a particular reason that you need to open it with a browser? It might be a better idea to open the file with an XML viewer or editing program, since they don't incur the extra overhead that a browser has.

 

[Senteaf]

Are you sure 77MB xml file is huge?

my clock speed should be fast enough, but I guess all that happens because I don't have a good hard drive.
thx anyway.

 

[TCG]

Opening a file that large in your browser can certainly cause issues. I would also recommend trying notepad++ as it will handle things like this MUCH better.

 

[cluberti]

Also, a 77MB XML file???? XML is mostly text, so what kind of application would create an XML that large? I'm not surprised browsers choked on it as they're going to try and *render* it, rather than just display it - imagine if you tried to render a 77MB *web page*. You'd have the same problem.

 

[Senteaf]

Okay I see...

I will try it in notepad++