Script ran too long - since 6.2.4?

[MunkDev]

I wouldn't know if it would work, because the error is too elusive. It might not be caused by the mask itself, but rather setting the mask takes so much time that the overall execution time in a certain scenario exceeds the limit. However, if the threshold is at 200 ms, then something is obviously very wrong, since 200 ms is a very long time for an action button update to run - especially for only 15 buttons. I'm not sure what's going on tbh, since I can't follow the trail any further than the state update from the secure handler.

[MunkDev]

So, while leveling up in combat, my bar updates an art asset that has a mask applied to it when PLAYER_TALENT_UPDATE fires. Since this is a completely separate process that has nothing to do with the action buttons or the childupdate of the bar, it must be the texture masking that's spawning this issue at random.

This is the offending line of code in that art update:

self.ArtOverlay:SetMask("Interface\\GLUES\\Models\\UI_Dwarf\\UI_Goblin_GodRaysMask")

How can this be reported to Blizzard? I guess it's not exactly a high priority issue, but masked textures not only create this issue in combat, but updating them can sometimes lead to a very noticeable stutter in framerate. There's obviously something inherently wrong with how that function works since it doesn't happen consistently.

[SDPhantom]

I guess you can file it as a bug report using this link.
http://us.battle.net/wow/en/forum/1012660/

[Resike]

I've never seen and blue respond any lua/xml releated issues there. But i'm 100% sure if you nag enough some GM will come and tell you to reset your interface.

[Fizzlemizz]

Originally Posted by Resike I've never seen and blue respond any lua/xml releated issues there. But i'm 100% sure if you nag enough some GM will come and tell you to reset your interface.

In their defence, the forum title is Bug Report not Bug Discussion

[Yukyuk]

Originally Posted by Fizzlemizz In their defence, the forum title is Bug Report not Bug Discussion

Very true, Amen

[Resike]

Originally Posted by Fizzlemizz In their defence, the forum title is Bug Report not Bug Discussion

Well you can't really handle bug reports without at least a small interaction. At least they should burp back things like: working on in, will look into it, it's working as intended, ghostcrawler said it's fine, or something.

[MunkDev]

I guess it might be of interest since it could potentially trigger off a portrait update. The portraits use the same masking technique as custom masks applied to textures, though it happens to be wrapped in a dedicated function. I've noticed stutters every now and then even with addons disabled.

[Fizzlemizz]

Originally Posted by Resike ghostcrawler said it's fine, or something.

We got the moose so I guess that's feedback