Details! Damage Meter

Details! Damage Meter

250M Downloads

BugBag bug catcher caught this bug

Quearrel opened this issue ยท 1 comments

commented

Before Start!

Make sure the bug also happen when Details! is the only addon enabled.

Game and Details! version
WD 10662 version 10.0.5

Describe the bug

  • Steps to Reproduce (what did you do to make the bug happen): Bugcatcher addon says a certain script ran for too long, there is also a bug with dungeons where I can't use my key bindings for spells, not sure if that's Details! related, though.

  • Result (what happens when you follow the steps above): All that happens is the script runs for too long, this happens during and after dungeons.

  • Expected (what you think the expected behavior would be when following the steps): enter a dungeon, do the dungeon, during this my Bugcatcher addon catches the bug. I have the bug logs.

  • When the bug started (a date, wow path release, details update, etc)? Has happened since 10.0.5 released

  • Additional information:
    Bug Catch Log;

2700x Details/core/gears.lua:3166: script ran too long
[string "@Details/core/gears.lua"]:3166: in function `UpdateAddOnMemoryUsage'
[string "@Broker_Memory/Core.lua"]:63: in function <Broker_Memory/Core.lua:59>

Locals:
currentTime = 1444653424.704500
(*temporary) = defined =[C]:-1
(*temporary) = 1444653424.704500
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = "script ran too long"
UpdateAddOnMemoryUsage_Original = defined =[C]:-1
bigStutterCounter = 0
stutterCounter = 42

Lua Error
Post here lua errors, if you aren't getting any, use /console scriptErrors 1 not sure if above is a LUA error or not :S

Screenshots
Post images of the bug if necessary.

Combat Log
Include a link to a combatlog file if the error is about not detecting a skill, usable item or item proc.
The log can be as simple as hitting a mob with white damage and using the item/skill.
not that I am aware.

Other Information
If necessary, add more info here. My bug catcher addon has been catching this for awhile now, and usually i just /reload and it's cleared. But it is consistent in continuing after dungeons and during them.

commented

Broker_Memory addon is calling UpdateAddOnMemoryUsage. Should probably not have that addon calling such an expensive function mid dungeon. Can cause lag