Possible related LUA error; weird behaviour in latest version
raysmith59 opened this issue ยท 7 comments
Three things that might be related:
- The Alerts frame has reset and isn't resizing; when I try to move it, it just snaps back to default; this happens after reset as well
- The Loss of Control and Game Menu checkboxes aren't saving with relog
- I'm getting a Blizzard LUA error when going into Edit Mode occasionally since the update, I don't know that it's related to the latest version but just in case:
6x C stack overflow
[string "=[C]"]: ?
[string "=[C]"]: ?
[string "=[C]"]: ?
[string "=[C]"]: ?
[string "=[C]"]: ?
[string "=[C]"]: ?
[string "=[C]"]: ?
[string "=[C]"]: ?
[string "=[C]"]: ?
[string "=[C]"]: ?
[string "=[C]"]: ?
[string "=[C]"]: ?
...
[string "=[C]"]: ?
[string "=[C]"]: ?
[string "=[C]"]: in functionShow' [string "@Blizzard_UIParentPanelManager/Mainline/UIParentPanelManager.lua"]:493: in functionSetUIPanel'
[string "@Blizzard_UIParentPanelManager/Mainline/UIParentPanelManager.lua"]:295: in functionShowUIPanel' [string "@Blizzard_UIParentPanelManager/Mainline/UIParentPanelManager.lua"]:174: in function <...ParentPanelManager/Mainline/UIParentPanelManager.lua:169> [string "=[C]"]: in functionSetAttribute'
[string "@Blizzard_UIParentPanelManager/Mainline/UIParentPanelManager.lua"]:888: in function <...ParentPanelManager/Mainline/UIParentPanelManager.lua:866>
[string "=(tail call)"]: ?
[string "@Blizzard_GameMenu/Standard/GameMenuFrame.lua"]:68: in function <Blizzard_GameMenu/Standard/GameMenuFrame.lua:65>
Locals:
(*temporary) = EditModeManagerFrame {
advancedOptionsEnabled = true
AccountSettings = Frame {
}
RevertAllChangesButton = Button {
}
LayoutDropdown = Button {
}
accountSettings =
}
modernSystemMap =
}
dirty = false
GridSpacingSlider = Frame {
}
numLayouts =
}
ShowGridCheckButton = Frame {
}
EnableSnapCheckButton = Frame {
}
editModeSystemAnchorDirty = true
Title = FontString {
}
fixedWidth = 510
snapEnabled = false
EnableAdvancedOptionsCheckButton = Frame {
}
modernSystems =
}
hasActiveChanges = false
Tutorial = Button {
}
Border = Frame {
}
registeredSystemFrames =
}
layoutApplyInProgress = false
FramesBlockingEditMode =
}
accountSettingMap =
}
SaveChangesButton = Button {
}
Grid = Frame {
}
MagnetismPreviewLinesContainer = Frame {
}
CloseButton = Button {
}
layoutInfo =
}
LayoutLabel = FontString {
}
}
(*temporary) = EditModeManagerFrame {
advancedOptionsEnabled = true
AccountSettings = Frame {
}
RevertAllChangesButton = Button {
}
LayoutDropdown = Button {
}
accountSettings =
}
modernSystemMap =
}
dirty = false
GridSpacingSlider = Frame {
}
numLayouts =
}
ShowGridCheckButton = Frame {
}
EnableSnapCheckButton = Frame {
}
editModeSystemAnchorDirty = true
Title = FontString {
}
fixedWidth = 510
snapEnabled = false
EnableAdvancedOptionsCheckButton = Frame {
}
modernSystems =
}
hasActiveChanges = false
Tutorial = Button {
}
Border = Frame {
}
registeredSystemFrames =
}
layoutApplyInProgress = false
FramesBlockingEditMode =
}
accountSettingMap =
}
SaveChangesButton = Button {
}
Grid = Frame {
}
MagnetismPreviewLinesContainer = Frame {
}
CloseButton = Button {
}
layoutInfo =
}
LayoutLabel = FontString {
}
}
Disregard for now, I think it's a conflict between EME and another addon called Move Anything. Disabling that one may have resolved these issues.
Well, just tried it in a bg and no errors. So, /shrug. This part of the error log:
[string "=[C]"]: ?
[string "=[C]"]: ?
[string "=[C]"]: ?
[string "=[C]"]: ?
[string "=[C]"]: ?
[string "=[C]"]: ?
[string "=[C]"]: ?
[string "=[C]"]: ?
[string "=[C]"]: ?
[string "=[C]"]: ?
[string "=[C]"]: ?
[string "=[C]"]: ?
...
[string "=[C]"]: ?
[string "=[C]"]: ?
suggests its probably an issue in the game engine. If it was an addon, it would usually be pointing to the line of code in the addon, not just be completely blank.
As for the loss of control and game menu: the checkboxes reverting to unchecked after a reload/relog is by design. The Loss of Control only displays properly if you've been affected by a CC since the last /reload, and the Game Menu gets in the way of everything.
So far I've only had this error when I enter a BG that has BG targets, like a flag carrier or temple of kotmogu. Since I can't just AFK the BG while I try and bugfix it, that makes this very difficult to investigate.
Think I found the problem: 6389212#diff-01a167ae8b73f0faaf442c5ede2063fafee83c4fb4f02f5836363e50d8da8621L11