209 - Lack of space causes WoW crashes
When there is not enough room on the bar to display all the data it wants, recount crashes wow.
What steps will reproduce the problem?
1. enable % of damage done to help take up room
2. choose a large font, such as White Rabbit
3. DPS a target
What is the expected output? What do you see instead?
The user expects to see "..." everywhere as a sign that more room is needed, or extending the frame, or even a graceful close as the error is caught. Instead, wow crashes altogether.
What version of the product are you using?
1121
Do you have an error log of what happened?
No log is created.
Please provide any additional information below.
I have a decent computer that can still show 30 FPS while aoeing the drakes in Sindy halls (I don't know if you raid but ~2 FPS is average), and I have most recording turned off. Recount crashed when I attacked a target dummy, something alot less strenuous on a computer than 25 aoes.
| User | When | Change |
|---|---|---|
| blackquaza | Oct 07, 2010 at 21:35 UTC | Create |
- 2 comments
- 2 comments
Facts
- Reported
- Oct 07, 2010
- Status
- New - Issue has not had initial review yet.
- Type
- Defect - A shortcoming, fault, or imperfection
- Priority
- Medium - Normal priority.
- Votes
- 0
- Component
- Recount
- Reply
- #2
blackquaza Oct 08, 2010 at 07:56 UTC - 0 likesthat makes sense: IF i was running the graphs, storing all possible data, and in icc. however, i was ungrouped, with MAYBE one other person beside me, casting Blizzard on the ogrimmar target dummies for 3 seconds - hardly a memory issue. Recount was only storing Boss, Player, and Grouped at the time. Also, changing fonts and removing the % dps solved the problem, which would not have if memory was the issue.
Crash occurs after i blizzard, regardless of how long i was online (the second attempt had me on for less that 2 minutes). im using the "GOOD" settings, with max view distance added and a custom "/console spelleffectlevel 100". several addons are running, though none of which seemed to cause any issues to any other players in the guild using recount. finally, no lua errors were reported, so i couldn't tell you that.
it could simply be the font though, ill play around with other large fonts and if its only that particular one, ill post to the blizzard forums.
and idk, curse said GO HERE so i WENT HERE and POSTED A TICKET.
- Reply
- #1
mysticalos Oct 07, 2010 at 22:10 UTC - 0 likesthis isn't a recount problem
it's a wow being a 32 bit app problem memory problem or an api bug problem
the app has a 2 gig memory limit, take that, factor in a high detail zone like ICC, you are looking at the app using 1.78 gigs of memory all by itself with graphics settings on ultra in raid combat. this doesn't factor in lua memory from other addons or memory spikes of raid combat. if you don't clear recount often, it's gonna eat up memory until the app runs out and crashes. it's also pretty well knwn wow has a memory leak too, the heap will grow over time from texture memory not being released. it's why wow usually always crashes, addons or not, after x amount of hours in an ultra setting.
addons can't crash wow, it's an imposiblity. if wow crashes from an addon, it's typically limitations of application itself. or a bug in app itself that addon ran into calling an api. so factor in how long wow was open, what grfaphics settings were, how many addons running, what lua memory size was. sure crash was a combination. if this is reproducable though, you probaly discovered a bug in blizzards font api and probably should post it on their bug report forum and ui/macro forum.
and edit, since when do ticket subscriptions work? guess i need to unsubscribe to that heh.