Random 'Tainted Execution Path' error

[FenixTX2]

Has anyone else ever run into a problem when using DoString to cast a spell which results in wow throwing something similar to the following?

ID: 4
Error occured in: AddOn: QuestHelper
Count: 1
Message: Error: AddOn QuestHelper attempted to call a forbidden function (CastSpellByName()) from a tainted execution path.
Debug:
   [C]: CastSpellByName()
   [string "CastSpellByName("Fishing");"]:1: in main chunk
   [C]: resume()
   QuestHelper\timeslice.lua:164: QH_Timeslice_Work()
   QuestHelper\manager_event.lua:129:
      QuestHelper\manager_event.lua:99

It appears at random intervals so far as I can tell.

[ramey]

You're probably not calling from main thread...

[Kryso]

Just a little theory (I did no research, and its probably all wrong):

I don't think its actually neccessary to call it from "main thread". I think everything including all lua scripts is by default called from main thread - so it's completely useless for wow to check what thread calls functions (except disabling calls with CreateRemoteThread). I think there are 2 states: one where you can call everything, and second (enabled when processing user lua scripts) where you can call only something. So when you call your DoString when state 1 is active, you are fine, however when you call it when state 2 is active, you get taint message.

Sorry if this is completely wrong :-)

[Nesox]

M-M-Monsterfail 1!

[ramey]

Just a little theory (I did no research, and its probably all wrong):

I don't think its actually neccessary to call it from "main thread". I think everything including all lua scripts is by default called from main thread - so it's completely useless for wow to check what thread calls functions (except disabling calls with CreateRemoteThread). I think there are 2 states: one where you can call everything, and second (enabled when processing user lua scripts) where you can call only something. So when you call your DoString when state 1 is active, you are fine, however when you call it when state 2 is active, you get taint message.

Sorry if this is completely wrong :-)

There are two states, but one for login screen and one ingame. It's obviously a threading issue, you aren't calling it from main thread.

The issue PROBABLY is that an addon is executing a chunk of lua code while you call DoString and that command is protected so the addon gets an error about being tainted because its thought that the addon executed it.

But yeah, you aren't calling from mainthread

[FenixTX2]

Thanks for taking a look at this.
@remey. Just for info: You're right, I'm not calling from the mainthread. My program first checks that no other addon is executing. When I get an all clear signal I pause the main thread, inject and execute using blackmagic and then resuming the mainthread. It works for around 10 minutes before I recieve an error such as the one above.

I'll look into executing from the mainthread.