TellMeWhen

TellMeWhen

24M Downloads

[CF 1415] Script ran too long

tmw-issue-import opened this issue ยท 5 comments

commented

I'm not sure this is yours.

 

1x [string "safecall Dispatcher[1]"]:9: script ran too long
[string "safecall Dispatcher[1]"]:9: in function <[string "safecall Dispatcher[1]"]:5>
(tail call): ?
TellMeWhen\TellMeWhen-8.3.3.lua:2662: in function `UpdateNormally'
TellMeWhen\TellMeWhen-8.3.3.lua:2783: in function `Update'
TellMeWhen\TellMeWhen-8.3.3.lua:2791: in function `?'
...s\AckisRecipeList\libs\AceTimer-3.0\AceTimer-3.0-17.lua:53: in function <...s\AckisRecipeList\libs\AceTimer-3.0\AceTimer-3.0.lua:48>

Locals:
func = <function> defined @TellMEwhen\Components\Core\Group.lua:424
(*temporary) = true
(*temporary) = "script ran too long"
method = <function> defined @TellMEwhen\Components\Core\Icon.lua:811
arg1 = TellMeWhen_GlobalGroup6_Icon36 {
0 = <userdata>
group = TellMeWhen_GlobalGroup6 {
}
ComponentsLookup = <table> {
}
Update_Method = "auto"
EventHandlersSet = <table> {
}
Modules = <table> {
}
attributes = <table> {
}
ID = 36
Name = ""
GUID = ""
Enabled = false
Type = ""
NextUpdateTime = 0
TempGUID = "TMW:icon:1PInBZVDkgh9"
UnitConditions = <table> {
}
typeData = <table> {
}
position = <table> {
}
lmbButtonData = <table> {
}
Events = <table> {
}
SettingsPerView = <table> {
}
viewData = <table> {
}
Conditions = <table> {
}
Components = <table> {
}
States = <table> {
}
}
xpcall = <function> defined =[C]:-1
call = <function> defined safecall Dispatcher[1]:3
eh = <function> defined @TellMEwhen\TellMeWhen.lua:457


Posted by CurseForge user solitha | Imported from CurseForge issue #1415 | Raw

commented

I also get the "script ran too long" error when my warrior jumps from Skyhold when using a profile that has a very large number of groups, icons, and conditions.  Toggling /tmw configuration on and off resumes normal TMW activity and all icons work again, however if scriptErrors are not on, there is no indication this occurred and many icons just appear not to work (and it may not be obvious right away).


Posted by CurseForge user canofbutter

commented

Blizzard broke something in 7.2.5, or otherwise made some sort of significant change without announcing it to the addon author community. Lots of other devs confused as well: http://www.wowinterface.com/forums/showthread.php?t=55496. Whether it was intentional or not remains to be seen, but nevertheless it has caused errors such as these in a number of addons.

 

Because there seems to be no rhyme or reason to it, there's not much I can do.

 

If you guys want to run this command and tell me if it causes the error (its basically equivalent to spamming /tmw a bunch, but without actually changing the locked/unlocked state), that could help, but even knowing whether it does or not doesn't explain why this is happening. The inconsistency of the issue makes it very unlikely that I'll invest any time into trying to figure it out.

 

/run for i = 1, 10 do TMW:Update() end


Edited Jul 3, 2017

Posted by CurseForge user Cybeloras

commented

Ran that script and did not receive an error.

 

I did a jump from Skyhold to Dalaran on my warrior and got an error:

 

Message: [string "safecall Dispatcher[1]"]:9: script ran too long
Time: 07/03/17 15:31:35
Count: 1
Stack: [string "safecall Dispatcher[1]"]:9: script ran too longInterface\SharedXML\SharedBasicControls.lua:204: in function <Interface\SharedXML\SharedBasicControls.lua:203>
[C]: ?
[string "safecall Dispatcher[1]"]:9: in function <[string "safecall Dispatcher[1]"]:5>
(tail call): ?
Interface\AddOns\TellMeWhen\TellMeWhen.lua:2651: in function `UpdateNormally'
Interface\AddOns\TellMeWhen\TellMeWhen.lua:2783: in function `Update'
Interface\AddOns\TellMeWhen\TellMeWhen.lua:2791: in function `?'
...\AddOns\DataStore\libs\AceTimer-3.0\AceTimer-3.0.lua:53: in function <...\AddOns\DataStore\libs\AceTimer-3.0\AceTimer-3.0.lua:48>

Locals: errorMessage = "[string "safecall Dispatcher[1]"]:9: script ran too long"
DisplayMessageInternal = <function> defined @interface\SharedXML\SharedBasicControls.lua:187
MESSAGE_TYPE_ERROR = 0


Posted by CurseForge user canofbutter

commented

Blizzard is aware of the issue and will be fixing it in 7.3: https://www.wowace.com/projects/weakauras-2/issues/981


Posted by CurseForge user Cybeloras

commented

I'm getting this error too whenever i zone into the old garrison, via the hearthstone.


Posted by CurseForge user Oxides