|
If there's any one thing I hate about the new secure frames system it's those error messages. Everything in that message tells me where the problem happened in Blizzard's code and contains nothing to tell me where in my code the taint occurred /sigh
Unfortunately, there's nothing I can do at this point because there's just no indication whatsoever where in the code this taint occurred. We'll need to keep an eye on this and see if we can find a pattern to it so I can home in on where it's originating.
Thanks for reporting it and *please* everyone, if you see similar errors, try to post here as well... the more detail you can provide the better.
|