Possible Memory leak with MQ2 20031203

RogerWilco · Post by **RogerWilco** » Wed Dec 03, 2003 10:32 am

I am not sure if it is MQ2 but I am having to scrub my RAM like crazy to keep it where it normally would be at... in the mater of 3 minutes I will have Zero RAM available...

I never had this problem until I complied the 20031203 verson.

Any thoughts or ideas??

just a question... im too tired and sick with the flu to look this up but when you are looking at the Window Task Manager on XP when it says memory usage... does that mean currently using or total used during the duration since the program was executed

<<<edited>>>

update: Memory loss still happens weither or not you are runnign a macro.

the problem seems to do with eqgame.exe according to the processes

unclebean · Post by **unclebean** » Fri Dec 05, 2003 12:17 pm

I've also been experiencing major performance issues after MQ2 has been running for a while. Have had had a Windows XP virtual memory warning pop up. Being forced to use MQ1 as this memory issue is causing EQ to be unplayable. Am using VS6 to compile, if that matters.

MacroFiend · Post by **MacroFiend** » Fri Dec 05, 2003 1:43 pm

RogerWilco, remove all plugins from your MacroQuest.ini file, restart MQ and EQ. See if you still see the memory leak. Then test each plugin one at a time until you find where the leak happens.

You'll need either MQ2Chat or MQ2ChatWnd to be your first tested and then keep those loaded when you test the others (or you won't get any output from MQ though mouse and face commands would work)

Once you know which plugin (or MQ2Main) is causing the leak, post back with that so the offending plugin can be looked at.

Also, make sure you are using MQ2-20031203a as your source.

Coraz · Post by **Coraz** » Sat Dec 06, 2003 12:03 am

Anyone get results on this? Takes me 30 seconds to fire up any file, web browsers, songs with mq2 running (the bastich!).

Lax · Post by **Lax** » Sat Dec 06, 2003 12:39 am

Unload plugins, figure out which it is and let us know. Also, are you running the newest release? Thus far nobody has provided any help for figuring it out, only mentioned that there is a leak somewhere.