There seems to be a memory leak in the lastest version of ACT. After several hours, it is using over 700mb of memory on my system and causes the system to run slowly. Anyone else experiencing this?

Be careful of calling memory usage a memory leak. But what exactly are you doing to cause this? I did some quick tests parsing a 40MB and 120MB log file(clearing encounters each time) and could only get 400MB of memory usage at best. ACT kept unallocating old memory when the GC deemed it necessary.



I also macroed my keyboard to iterate through all tables and graphs in memory, but I could not get memory usage to increase at all. So I have to ask... what exactly are you doing?

Just had ACT running in the background while I was soloing / grouping. I also run the double attack plugin, not sure if that would have anything to do with it.

Perhaps it was just consuming a lot of memory due to the log file getting large without being split due to long eq2 sessions. I noticed the log file was 128mb. Could be it was just trying to load to much information and not an actual memory leak. I'll keep any eye on it and see if it happens again.

The size of the log file means almost nothing. The only thing affected is the Master File Table entry of the file. ACT reads from the end of the file and onward as it becomes available. It could be 1MB or 1TB and there would be no difference in ACT's behavior(assuming it can find the Zone Name within 1MB). EQ2 nor ACT actually cares how large the log file becomes... only Windows does when it has to update the MFT with all of the hard disk sectors the file occupies. That should not be an expensive procedure, nor will it take any memory.

I cannot think of what the Double Attack plugin could do to increase memory.