Compactframe Error Taint Issue?

Guides UI and Macro
1

I didn’t change much just updated some addons but whenever I enter a dungeon or instance it still gives this type of error all the time, and it doesn’t identify which addon is causing it.

A reload will fix it but really want to squash this one. Any tips or thoughts might help as it could be any of a few.

2

If you can reliably reproduce the issue then do a “divide and conquer” approach to your issue

  • disable half your addons and attempt to reproduce the issue.
  • if the problem goes away, enable half of what you previously disabled, and try to reproduce the issue
  • if the problem doesn’t go away, disable half of what’s remaining, and try to reproduce the issue.

You get the idea.

3

  • start wow

  • enter the following on the chat line (copy and paste it)

  • /console taintLog 1

  • exit wow

  • start wow

  • play until you get the error

  • quit wow

  • move (or copy) the ...\World of Warcraft\_client_\Logs\taint.log file to a safe location

note: the log files are overwritten at each game load so if you dont do this step then the file you upload wont contain the error

  • start wow

  • enter the following on the chat line (copy and paste it)

  • /console taintLog 0

  • exit wow

  • check the taint.log file (the one in the safe location) and find the error

  • find the error at the end of the file, it should tell you which variable/command was tainted

  • from the start of the file look for that variable and when it was first tainted, and by which mod

  • double check that previous taint didnt cause this taint - ie it can chain through shared libraries so track it all the way back

  • if you can find it then report it to the author of that mod

  • if you cant find it then try harder

there is a level 2 of logging, its a lot more verbose but can help in situations where you cant quite work out where the taint is coming from.

1 Like
4

Thanks. Seems like it’s the addon litemount. Already submitted a bug report.

Seems like there are some major issues with this as it’s a shared library and addon authors are all saying it’s not their addon and it’s hard to track. Oh well lol.