Authors CurseForge

So how do you explain your 20MB log of a full BT clear? I mean I believe you, you know the addon better, but there seems to be a discrepancy here...

EDIT: Ok I see you said 20 MB addon memory, so I guess a 40 Mb resulting file? That's not that far from mine, which is for 7 bosses.

Just to be clear, WoW does handle that much data without problems. I could have kept raiding all night and ended up with a bigger memory usage than that above. The problem only manifests itself when loading the savedvars. I do think Blizzard screwed up something.

I have 4 GB of RAM in my computer. That should be plenty. Also, while I agree that this isn't a huge amount of memory being used, it did seem a little excessive for only 7 bosses. I mean the SV file has way over a million lines (not home right now to check the exact number).

Quote from ms998

Is there an easy way of tracking crafting cooldowns in one easy place. I get the countdown if I'm logged on, but none if I log on after the cooldown has expired.

Go the Skills section where all your characters skills are listed. Mouseover the one you're interested in, it will tell you what's on cooldown or if they're all up for that particular profession and toon.

Ok, the memory issue thing.

Tonight, full clear of ToC-25 + first 2 bosses of Ulduar-25 (because Razorscale is the weekly raid quest on our realm). Running with default settings, I believe. Meaning keep boss segments only. Only setting I change is the 5 fights kept limit. I always increase that. In any case, that's a total of 7 bosses for tonight.

I decided to try a reloadui after all that. Got another wow.exe crash sending me back to the windows desktop. Here's the message I got before hitting the Send button for Blizz:

This application has encountered a critical error:

Not enough storage is available to process this command.

Program: C:\Users\Public\Games\World of Warcraft\WoW.exe
File: d:\buildserver\wow\4\work\wow-code\branches\wow-patch-3_3_0_b-branch\engine\source\blizzardcore\blizzardcore\source\system\memory\MemoryStorm.cpp
Line: 64

Requested 35243907 bytes of memory

35243907 is the exact size of my Recount's savedvar file after the reloadui. In other words, when I did reloadui, it saved it, tried to reload it... and failed miserably.

What bothers me is the size of the file. 35 MB for 7 bosses? You said you had a full clear of BT log that was 20 MB. Something seems wrong there.

That doesn't mean WoW shouldn't be able to load that though. After the crash, I was able to log in without a hard crash, but of course, I got the memory block too big error and Recount's empty.

I can't pretend I understand your table structure in the savedvars, but there seems to be a lot of info about deaths. I could be wrong, but it appears the RecountDeathTrack plugin uses the same SV file. Could it be what's bloating it? Just an idea since I have that plugin...

I have the 35MB file if you really want it, btw.

Elsia, would it be feasible for you to write a dummy addon that auto-fills a table with similar in structure to Recount's with random data, saves it, then tried to load it at logon again? That might provide you with some ideas of the cutoff point.

Other than that, I'll see if I can catch a file causing the problem.

I don't get d/c'ed often. The last time it happened was at the end of ICC (what's available of it anyway), after killing Deathbringer Saurfang and watching the scripted event. It took quite long for the game to kick me out, as it was writing all the SVs, including Recount's. That was the first or second week after ICC had come out, so it was a long raiding night with many attempts on bosses before finally clearing, so it made for a lot of data to write. Plus the game had been running for several hours, which probably didn't help the time it took for wow to kick me out cleanly.

Anyway, finally got kicked out to the login screen, tried relogging, the game crashed. As in wow.exe, not a lua error. Tried again, same thing. I deleted Recount's SV for that character and I was able to log back in. That's the worst I've ever had. Usually it's a lua error.

As to memory usage, I guess I could check the memory usage after every boss fight (or after every 5-man), then do a /reloadui and hope for a failure?

I get that too. It's to the point that I automatically wipe Recount before logging off, without even noticing I'm doing it.

I'm fairly sure I run with the default settings, but I'll double-check that when I can.

What kind of info do you need?

This also happens to me. I can't remember if it happens with raids or not, but it does in 5-mans. I would start there, rather than raids.

Quote from Adirelle

Ok, so I surely overlooked something (at least the previous 313 pages) : apparently, there is an option to have recount records buffs/debuffs uptimes but I can't get how to display them.

I asked about it a long time ago. The option is there but doesn't do anything. Yet?

Pitbull 4 does. I'm sure there are others.

Blah, they don't know what they're talking about. Check around this forum, it's well known. Pitbull 4, for example, has removed/renamed that option from the menu to stop people reporting it as a bug when it's really a Blizzard issue. Use /focus to focus something if you use a unitframe addon.

The cleaning out WTF folder trick always amuses me...

Read the WHOLE thread before posting, enderniniel. This is a blizzard bug.

I'm not sure if that matches your needs but have you looked at the Datastore collection of addons by Thaoky (on curseforge), that Altoholic uses as backend?

Are you guys running Little Wigs? Because this is now causing the "you are not in a raid" spam because we're apparently not allowed to send raid warnings in parties anymore, even as party leader. Assuming you have the Broadcast option turned on in Big Wigs.

It appears that you cannot send raid warnings in a party anymore, even as party leader, resulting in "You're not in a raid group" spam in chat.

EDIT: I do have the Broadcast option turned on in Big Wigs obviously.