A forum for reporting bugs NOT related to custom plugins.
Moderator: MacroQuest Developers
-
DreamKing
- a lesser mummy

- Posts: 79
- Joined: Tue Jun 10, 2003 12:29 am
Post
by DreamKing » Tue Nov 25, 2003 11:31 pm
There's definitely some issues with MQ2 memory. My normal memory usage with MQ1 was about 500mb. Presently, after having run MQ2 about 3 hours, I'm using 1.12gb memory.
Is it just me?
(Latest build by the way)
-
Lax
- We're not worthy!

- Posts: 3524
- Joined: Thu Oct 17, 2002 1:01 pm
- Location: ISBoxer
-
Contact:
Post
by Lax » Wed Nov 26, 2003 1:29 am
Hmmm 1.12gb is excessive yes. Are you looking at the eqgame.exe process memory usage or overall?
-
Falco72
- a hill giant

- Posts: 215
- Joined: Fri Sep 26, 2003 3:24 am
Post
by Falco72 » Wed Nov 26, 2003 1:24 pm
I had the same problem. Using MQ2 on three Win2000 computers, each eqgame.exe is using more than 600 mb, after about 3 hours of playing. Using MQ1 I never had more than 200 mb of usage for single eqgame.exe. And I havent changed anything in eq setting.
I found this problem today after a very bad pull in PoS and a fast Succor, all my three computers frozen trying to reload the zone. I had to reset all of them.
-
Lax
- We're not worthy!

- Posts: 3524
- Joined: Thu Oct 17, 2002 1:01 pm
- Location: ISBoxer
-
Contact:
Post
by Lax » Wed Nov 26, 2003 1:42 pm
Try turning off plugins one at a time. MQ2Map is the first one that comes to mind. Turn that off on one and see if it stays normal while the others dont
-
DreamKing
- a lesser mummy

- Posts: 79
- Joined: Tue Jun 10, 2003 12:29 am
Post
by DreamKing » Wed Nov 26, 2003 2:06 pm
Lax wrote:Hmmm 1.12gb is excessive yes. Are you looking at the eqgame.exe process memory usage or overall?
The total was 1.4gb by the time everything eventually just froze up and I had to kill EQ. Memory usage instantly dropped from 1.4gb to 220mb. I didn't really have anything else out of the ordinary running.
I was looking at overall usage in addition to eqgame.exe. Overall was 1.4gb and eqgame.exe was showing up about 440mb in the process list. I can't remember exactly but it was much higher than usual.
I saw a suggestion by someone in another post that they turned off debugspew. I'll try that tonight and see what happens.
-
Lax
- We're not worthy!

- Posts: 3524
- Joined: Thu Oct 17, 2002 1:01 pm
- Location: ISBoxer
-
Contact:
Post
by Lax » Wed Nov 26, 2003 2:18 pm
debugspew isnt going to cause a memory leak. try what i suggested...
-
in_training
- Craptastic
- Posts: 115
- Joined: Fri Oct 10, 2003 8:25 am
Post
by in_training » Wed Nov 26, 2003 2:32 pm
Same is happening for me. Unloading map seemsd to help with speed. in the process of testing now. but there's something not so right somewhere.
It's using alot of memory..
Sorry for being so vague Lax, I'll try to get more specifics.
-
morannon
- a lesser mummy

- Posts: 57
- Joined: Sun Nov 03, 2002 3:50 pm
Post
by morannon » Wed Nov 26, 2003 3:52 pm
Mine hit 820 mb used for eqgame.
From a fresh login, it starts at around 432MB used and grows 16-20k /sec -- with just EQLabels and EQ2ChatWnd loaded.
EDIT : Removing mq2labels (which I hate being without!) halted the memory usage increase dead.
Well, its still increasing at about 8k / minute
-
ml2517
- a grimling bloodguard

- Posts: 1216
- Joined: Wed Nov 12, 2003 1:12 am
Post
by ml2517 » Wed Nov 26, 2003 4:05 pm
Are the people having the memory leaks all using custom UI's? That have MQ labels in them?
Try switching to the default UI and see if you get the leak. I'm not noticing a leak on my systems from what I can tell.
-
morannon
- a lesser mummy

- Posts: 57
- Joined: Sun Nov 03, 2002 3:50 pm
Post
by morannon » Wed Nov 26, 2003 4:08 pm
I am -- but whats the point of mq2labels if you arent using a custom ui =)
-
ml2517
- a grimling bloodguard

- Posts: 1216
- Joined: Wed Nov 12, 2003 1:12 am
Post
by ml2517 » Wed Nov 26, 2003 4:27 pm
Nothing

The whole point was to reinforce your theory of it being MQ2labels that was the culprit.
-
Lax
- We're not worthy!

- Posts: 3524
- Joined: Thu Oct 17, 2002 1:01 pm
- Location: ISBoxer
-
Contact:
Post
by Lax » Wed Nov 26, 2003 4:55 pm

it's an offset problem. OHMZ WHERE ARE YOU, ITS TIME FOR YOUR FLOGGING. The CXStr__operator_equal1 is incorrectly the offset for CXStr__CXStr3... so basically it's creating another string instead of setting the existing one.
this will be fixed shortly.
-
Lax
- We're not worthy!

- Posts: 3524
- Joined: Thu Oct 17, 2002 1:01 pm
- Location: ISBoxer
-
Contact:
Post
by Lax » Wed Nov 26, 2003 5:54 pm
CVS server not letting me in, until then here's the fix.
eqgame.h
Code: Select all
#define CXStr__operator_equal1 [color=red]0x00587650[/color]
recompile MQ2Main and you're set
-
Lax
- We're not worthy!

- Posts: 3524
- Joined: Thu Oct 17, 2002 1:01 pm
- Location: ISBoxer
-
Contact:
Post
by Lax » Wed Nov 26, 2003 6:06 pm
Zip updated.
-
Elric
- Cheese Whore

- Posts: 466
- Joined: Sun Nov 23, 2003 12:31 am
- Location: Tampa, Fl
-
Contact:
Post
by Elric » Thu Nov 27, 2003 1:49 am
Oh thank god. I just noticed the mem leak too. About 1.1 gigs of mem... good lord. Hehe