Lagspikes when entering combat and/or using rogue abilities after an Bigwigs Lua Error
Sylux1992 opened this issue ยท 3 comments
Describe the problem
Sometimes after you switch some talents or to a different loadout and enter a fight you get lagspikes. I tested a few things on my rogue and once it's happening i get lagspikes with every shadowstrike from stealth, entering/exiting shadow dance and sometimes shuriken storm. I grabbed Bugsack to identify the problem and the error message below popped up. I tested it in the orgrimmar dungeon.
What steps will reproduce the problem?
- Switching talents, loadouts
- Entering combat
- Some rogue abilities
Consider attaching a screenshot below to help describe your issue (Attach directly, do not link to other websites)
What version of BigWigs are you using? (Stating 'latest' is not useful)
Bigwigs-v264
Do you have an error log of what happened?
1x [ADDON_ACTION_BLOCKED] AddOn 'BigWigs' tried to call the protected function 'MultiBarBottomLeft:SetPointBase()'.
[string "@!BugGrabber/BugGrabber.lua"]:480: in function <!BugGrabber/BugGrabber.lua:480>
[string "=[C]"]: in function SetPointBase' [string "@FrameXML/EditModeSystemTemplates.lua"]:126: in function
SetPoint'
[string "@FrameXML/EditModeManager.lua"]:638: in function <FrameXML/EditModeManager.lua:617>
[string "=[C]"]: in function UpdateBottomActionBarPositions' [string "@FrameXML/EditModeManager.lua"]:564: in function
UpdateActionBarLayout'
[string "@FrameXML/EditModeSystemTemplates.lua"]:743: in function UpdateGridLayout' [string "@FrameXML/StanceBar.lua"]:73: in function
UpdateState'
[string "@FrameXML/StanceBar.lua"]:25: in function `Update'
[string "@FrameXML/ActionBarController.lua"]:81: in function <FrameXML/ActionBarController.lua:55>
Any additional information? (example: WoW language if not English)
The other addons I used are Bartender, Weakauras, Icehud and MethodRaidTools. Everything else was disables.
BigWigs has nothing to do with your action bars (mentioned in the error). Please try with only BigWigs enabled and see if the issue still exists.