Do LUA addons execute in Wow's main thread?

[ggg898]

Question in topic...
Got some strange things going on which look as threading issues...

[Cypher]

Are you seriously asking this? No.. really.... seriously?

[MaiN]

Are you seriously asking this? No.. really.... seriously?

What's so weird about this question?
AFAIK macros and text gets executed in the main thread.
Try typing this ingame:

/run for i=0,10000000 do for t=0,1000000 do end end

That will freeze WoW for a really long time - but why would Blizzard allow addons to freeze WoW's main thread?

@OP: I believe they do. Apoc posted a thread about hooking the OnUpdate script event for addons, which is basicly like an EndScene hook - it should be called from the main thread.

[ggg898]

I dont realize it is such a stupid question.

I dont know if LUA parsers are threaded, if all LUA addons are executed side by side or one at a time, stuff like that ...

I would say without knowing anything about it, that that the main thread probably fires the frame update event syncronously, but i dont know for sure, hence asking.

[ggg898]

@Main, thanks i have looked but i didnt find that info. I tried to do stuff like that. Call a custom lua command from an addon instead of endscene hook (or actually both during development) but some strange things happened, thats why I Just wanted to make sure the the Addon was executing in the main thread...

[FenixTX2]

@MaiN: It makes sense for for loops to pause the main thread until completion, otherwise people could use them as a crude timing method for macro based bots.

[MaiN]

@MaiN: It makes sense for for loops to pause the main thread until completion, otherwise people could use them as a crude timing method for macro based bots.

That's true, but not really. It's still easily done by using OnUpdate.

[ggg898]

Think I can answer this one myself... and the answer is... No...

(Or maybe No... really... seriously... ;P)

GetCurrentThreadId returns different ids when called from Lua addon and from endscene hook.

[suicidity]

Lua is not Multi-Threaded capable, at least not in it's current incarnation. Lua must be called from the Main Thread of the game.

[ggg898]

So... How come I got the result I got from my little test?

1. Reg you Lua function which just call GetCurrentThreadId(), call that func from Lua addon
2. Call GetCurrentTreadId() from endscene
3. Compare, at least I get diffent ids...

[flo8464]

Another reason it has to be executed by WoWs mainthread is that all relevant game-information is stored in the mainthreads TLS.

[Robske]

So... How come I got the result I got from my little test?

1. Reg you Lua function which just call GetCurrentThreadId(), call that func from Lua addon
2. Call GetCurrentTreadId() from endscene
3. Compare, at least I get diffent ids...

[Cypher]

Another reason it has to be executed by WoWs mainthread is that all relevant game-information is stored in the mainthreads TLS.

Ladies an gentleman we have a winner!

1. The object manager is thread-local and only available in the main thread.
2. Lots of the Lua callbacks rely on the object manager.
3. Ergo, Lua must be executed in the main thread.

Lua is not Multi-Threaded capable, at least not in it's current incarnation. Lua must be called from the Main Thread of the game.

This too.

[ggg898]

@robske, Ok thanks, must be something strange that messed up my test.

And thanks to all other too taking time. Thought about the TLS but was confused by my test, which must have been f****d up.

[monko]

Are you seriously asking this? No.. really.... seriously?

Just stumbled upon this thread from Google. Just wanted to let you know you look like a massive dickhead