Comments about GrimReaper

Comment #7

no-reply@curseforge.com (Zeksie) — Fri, 28 Aug 2009 10:06:22 +0000

Even after a short fight, the combat log still contains the previous fights until some 5 minutes previously. The health storage has to go back to the start of the log. Which is why the usage is continuous over time.

Nothing is kept that is not required. And anyhing discarded is re-used. It's that simple. And to be honest, 5-7mb is really not a lot for what it's doing.

Comment #6

no-reply@curseforge.com (Daiyara) — Wed, 26 Aug 2009 11:01:30 +0000

ExcaliburClan,

do you have any link for your 'trashman' addon? I just use a simple file that tries to free the virtual memory when I click on it, but I need to minimize WoW to use it, so an addon would help a lot, specially with the high memory usage of Recount, GrimReaper and Decursive.

Comment #5

no-reply@curseforge.com (ExcaliburClan) — Mon, 24 Aug 2009 11:09:52 +0000

No its not as bad, but i think i should provide just abit more info so we are talking about the same thing.

GrimReaper seems to allocate memory over time that is not put to the garbagecollection at all.

In order to try to improve my comps poor performance, i discovered that garbage indeed do accumulate a little over time, and i tested if doing a full garbagecycle would improve things - it did. So i wrote an addon (Trashman) that every 15 seconds force a full garbagecycle, and this helped alot. some addons do creep alittle on garbage, those addons was stopped by this added garbage handling. I do find it odd that this indeed improves my performance, but i suspect the low memory forces virtual memory swaps to a lesser degree doing this... bad comp, ill fix that later.

However GrimReaper seems to lock the memory- i checked the code and found what i think is some time-delete data code for 2 hours, setting down the time-limit to 15mins helped some but didnt fix the full problem, and it seemed to cause some other problems aswell.

In raid i use up about 17-18mb addon memory. With my Trasman running it keeps pretty much in check over the course of a full raid. Using GrimReaper however starts off at some measly 0.1mb or something, and can grow as high as 7-8mb wich is not released in the course of the raid. This is the memory buildup i am referring to.

Some memory buildup is necessary,as it shows logs from recent events for a multitude of players, i understand that, but seeing the tooltip show full data for every player after a short fight, and GrimReaper having allocated maybe 0.2-0.3mb more memory, it seems holding 7-8mb after a raid is excessive.

Comment #4

no-reply@curseforge.com (Zeksie) — Tue, 18 Aug 2009 14:18:14 +0000

Well. This is not as bad as it used to be back in the old days of WoW. New incremental garbage collection reclaims garbage as it's needed all the time. But I'll have a look through it, see if something can be improved without much effort. But, it could be just that this is the running level of GrimReaper. It does have to store a historical health log of entire raid for the duration of your combat log (usually around 5 minutes worth).

Comment #3

no-reply@curseforge.com (ExcaliburClan) — Wed, 01 Jul 2009 09:29:18 +0000

The addon seems to accumulate memory over time that is not released back. Would it be possible to have the data no longer used to be released? I would suspect tables populated with combatlog data, but not releasing back data that is no longer shown in the tooltips.

My computer is old and with only 1GB RAM, i should buy a new one but cant afford atm. With some hands on i can however run WoW well in raids, as long as the addons dont start to consume memory. 2 very usefull addons seems bad at this, GrimReaper and Recount - both suffering from the same tendency to allocate more and more memory that is never released back even after the data is no longer used.

GrimReaper is such an excellent analysis tool for a healer that i really want it to work well, but the memory hog currently prevents me to use it on a permanent basis, or i have to do alot of handson activities to force the memory to be released.

Comment #1

no-reply@curseforge.com (teencute) — Tue, 17 Feb 2009 17:47:45 +0000

GOOD GOOD