Anyway, here’s some example code of how to repro this bug

function init() {
adXML = new XML();
adXMLfile = “xmlfile.xml”;
loadXml();
}
function loadXml() {
adXML.load(adXMLfile);
adXML.onLoad = function(sucess) {
if (sucess) {
init();
pass++;
output.text = pass;
}
};
}
init();

I possible, offload the parsing of the xml to your server. If you have it aggregating it on a cron each week, don’t just mirror the xml to your server, but parse it as well. You could parse the xml into a php version of same data type that you are currently deserializing it to on the client side. You could save this data as serialized info on your server. Then when a client requests the info you could have a PHP script read in the data and send it to the client via Flash remoting. You would take one hit each week for the processing, and a lot less intensive hit each time someone made a request. You aren’t serving flat xml files anymore, but from the clientside you don’t have the same issues.

http://www.swgcraft.com/resourceexport.php

26 different 300k files vs. one 7meg one

Each XML file is loaded individually, parsed into a tiny object, and the process continues until all 26 are done.

I could off-load to the server, but then… it’s already abstracted to simple XML that I can easily parse and then save locally to a local shared object. I only need to do this once a week for the user.

Do you have 9 different views or is each XML file parsed and then compiled into a single data source? If so you may want to consider offloading the parsing to the server.

What are you using to monitor your mem usage? Perfmon?