Well I can explain this one. One sentence "Fundamental flaw in the way the windows was designed". Seriously the whole "Not Responding" thing in windows is a pile of well you get the idea. They made some bad decisions when creating the OS and so you get totally meaningless status reported back to the OS. If anything that is a MS bug report (but er I wouldn't bother .PyroMancer2k wrote:In an attempt to replicate that lockup of MT I had. Which I mentioned in Maptools section telling everyone to save often . I tried to think of a way to quickly fill up memory. Since I was doing a LOT of debuging on macros I noticed that the memory in MT seems to get larger over time. Other then a memory leak the only thing that I figure which could account for this is chat box. So I tested with my "CRASH MT MACRO". Or at least that's what I named it hehe
You only need to run it like 3 times in the MT 256MB and it brings MT to it's breaking point. It does take several seconds to run but it also does a nice job of filling up the memory. Double-clicking on the green memory allocation bar does not free up the memory either.Code: Select all
[C(200),CODE: { [C(200),CODE: { THIS IS MEGA SPAM!! BRING ON THE SPAM!! OH YEA CRAZY SPAM!! <BR> }] }]
Also after 3 tries I found it locks up everytime if you run the macro 3 times then type /clear in order to clear the chat box which is the common method for freeing up the chat box's memory usage which I tested after running it only 2 times.
Next I noticed SEVERAL other odd things that happen when I do this. First off is even though in the task manager it says "Not Responding" next to MT in the process section you can see the javaw.exe file using up over 50% processing and 300MB memory with it constantly changing so it seems to be doing something.
This one is strange.PyroMancer2k wrote: But then a SECOND tab for MT appears on the task bar even though no new MT have started running or show up in task manager. Then a little bit after that the MT with java icon next to it appears on the tab bar which is the same one that runs on startup of a new copy of MT running. It then stays on their for a while then disappears for a second followed by it reappearing. Also like it was trying to start another copy of MT.
I wonder if this is really a big issue. After all if you were to try and type in all of the above that your spam macro created it would take someone who can type 70wpm about 4 days to type (and that's straight no resting).PyroMancer2k wrote: I know some people want to keep all their chat info but perhaps we could have an option in settings that would out the oldest messages after a curtain point say maybe it uses up 1/2 of the memory that way if you run the 1GB setup you can have a larger stored chat boxed before it starts clearing out the old stuff. Also if it's an option in settings people can choose if they want it to auto manage their chat logs from getting to large.
With debugging when the build with macro dialog boxes comes out you could always create a temporary dialog box and send all output to that (it allows all the same formatting as the chat window). If it is a temporary dialog box when you click on the close button the memory is no longer held so could be garbage collected (unlike text in chat box).