i think we need to try to fix this

09/30/2005 13:41 evulhotdog#1
this is wad we need to fix, the memory leak
09/30/2005 21:59 Makien#2
holly-cow, 140k for conquer....i rarly get 40k...why so high?
10/01/2005 01:25 ultimatedestroyer#3
Mines not that high either. 0.0
10/01/2005 01:29 vladi#4
@evulhotdog: are you using an amd athlon processor?
i know that when ur athlon is running for a long time when you do nothing on it (like when ur sleeping/away) your pc has a huge lag when you start "working" on it again
10/01/2005 02:41 evulhotdog#5
noppers, and i had 240k when i woke up thismorning....jesus i thought my computer was gonna explode :rolleyes:
10/01/2005 02:47 Peach#6
was it coz of tg?
10/01/2005 02:50 evulhotdog#7
dur.....of course
10/01/2005 04:41 DeathWalker#8
It is mainly because when CO starts up, it takes up alot of memory space.Try opening the window and open Co and see how much it takes up ^^
10/01/2005 06:15 imported_i_r_baboon#9
Quote:
Originally posted by DeathWalker@Oct 1 2005, 04:41
It is mainly because when CO starts up, it takes up alot of memory space.Try opening the window and open Co and see how much it takes up ^^
nope its when u run it for a long time as u keep it open more gets loaded into memory

memory leak fix = close conquer
10/01/2005 06:15 Peach#10
yeah.. conquer has memory leak problem
11/16/2005 20:08 CrackerJacker#11
I woke up this morning and my co was takeing up 400k memory even after it had been dced. i only had one running. and he was in tg.

I NEVER had this problem with co1 and it normal caped at around 140k per window.
i was able to run 5-8 co clients at the same time but with co2 i can't even keep 1 client open over night

if co was going to fix it the would have done so before releaseing it unless all the impatient people made them release premature. and if that is so then it will never be fixed cause co doesn't know how to fix bugs that don't affect db buying.
11/16/2005 22:01 Qonquer#12
from what i can gather, the CO client is a mish-mash of purchased modules all nailed together by a group of folk with limited knowledge of MFC. Yea granted there is some custom code in there, but most of it appears to be off-the-shelf technology. I doubt there's anyone with enough talent at TQ to track all the memory allocations that are not being freed.
11/16/2005 23:27 fallenStar#13
You can have a quick and ditry solution to that memory hungry CO2 clients by using one of those RAM optimizer program to free up those ram that CO2 client is holding.

You can try out this :
[Only registered and activated users can see links. Click Here To Register...]

Or this :
[Only registered and activated users can see links. Click Here To Register...]

Of course, these programs are only helpful when you have large size of RAM which i reckon maybe 384MB and above. Since if you RAM size if smaller, the program will keep refreshing or releasing the memory and slow down your system. Anyhow you are free to try. :)

Just my 2 cent. Hope TQ can fixed it soon. :rolleyes:
11/16/2005 23:46 CrackerJacker#14
tq won't fix it! why?
because they don't see any problems with it.
you aren't supos to leave your comp connected over night because you can get hacked or something.
and they made tg not so people could afk in it but so people can be at the computer playing in there.

this is what i have seen i will check out those memory things i am going to try the effects removel thing too mabe that is the key.

EDIT: i noticed the ram optimizer said windows xp already has one built in and therfore these are worthless for xp. i don't have xp so lets see. but if people on exp are still haveing memoryleak problems then this might not be the solution.
11/16/2005 23:57 CrackerJacker#15
it seems like this will work for the extra memory useage not to tweek with the automatic setting and see if i can stay connected all night