Lua error 7.1.0 #146


  • New
  • Defect
Open
Assigned to xuerian
  • _ForgeUser733470 created this issue Oct 26, 2016

    What steps will reproduce the problem?

    1. Lua error randomly

    What is the expected output? What do you see instead?

    Lua error

    What version of the product are you using?

    7.0-12

    Do you have an error log of what happened?

    2x [ADDON_ACTION_BLOCKED] AddOn 'XLoot' tried to call the protected function 'MultiBarBottomLeft:Show()'.
    !BugGrabber\BugGrabber.lua:573: in function <!BugGrabber\BugGrabber.lua:573>
    [C]: in function `Show'
    FrameXML\MultiActionBars.lua:37: in function `MultiActionBar_Update'
    FrameXML\InterfaceOptionsPanels.lua:1185: in function `setFunc'
    FrameXML\InterfaceOptionsPanels.lua:89: in function <FrameXML\InterfaceOptionsPanels.lua:85>
    [C]: in function `pcall'
    FrameXML\InterfaceOptionsFrame.lua:217: in function <FrameXML\InterfaceOptionsFrame.lua:216>
    [C]: in function `securecall'
    FrameXML\InterfaceOptionsFrame.lua:252: in function <FrameXML\InterfaceOptionsFrame.lua:248>

    Locals:

  • _ForgeUser733470 added the tags New Defect Oct 26, 2016
  • Xuerian posted a comment Oct 26, 2016

    Is there any reliable way to cause this to happen?

    Does this happen if you have XLoot Master disabled?

    If there's no reliable way, this is probably the unfortunate side effect of the way Blizzard implements the configuration window, but I'm glad to look into it regardless. Additionally, since it's usually the last to load, it can also be other addons using the Ace3 libraries also embeded in XLoot causing the issue, which then gets blamed for it.

    Again, glad to look into it with some more information, but if it's not reliable tends to be the kind of thing that is pretty hard to get fixed.


    Edited Oct 26, 2016
  • _ForgeUser733470 posted a comment Oct 27, 2016

    i have Xloot Master , Xloot Monitor and Xloot Frame disabled since i really only need the Xloot Group + options module :p.

    As you said this could simply be a random taint error from Ace3 , i will try and give more information if / when this happens again.


To post a comment, please login or register a new account.