Spring RTS Engine

Infolog hit 57mb, full of this:

Related: https://github.com/Tarendai/Shard/issues/8

Thanks for the update Tobi. Is there anything I can do in the meantime, or do I just need to hold my horses and wait till it's sorted?

I was wanting to make some more youtube vids, but it's not like the sky will fall if I don't get to them right this second

No need to do anything unless you have a good guess as to what the cause is: As far as I know no one yet has a clue why this is happening

(looks a bit like memory corruption, but valgrind didn't find anything)

Try using my last VS build, I'm not sure if it still works though as nobodies given feedback

Could this be related at all to how Shards lua vm is being linked in and possible crossover with springs own lua vm fork?

I considered that option, but dismissed it as unlikely since in Shard you integrate Lua as C source code, while Spring integrates Lua as C++ source code, so Spring's Lua has all its names mangled. (I also checked this using nm and/or objdump)

i hopefully fixed the issue...

@Forb: can you please try if http://springrts.com/dl/buildbot/defaul ... -gb9e0932/ works? (either the portable or the minimal portable)

Just saw this. I'll give it a shot today and report back. Thanks :)

Loads up fine, does nothing. Infolog: http://pastebin.com/F2JRuzUj

One thing interesting to note. First time I started, there was an issue with unit_scripts.lua (ya know, the gadget that loads lus), so I removed it as all my scripts are COB. However, while it didn't crash the game, It took out the gadget handler.

It took me a minute to realize that the gadget handler was toast, and before I figured that out I had spawned a commander on both sides. When I spawned one for shard, it started building and stuff.

ok, thanks for testing. the endless loop seems to be fixed. that it does nothing ... hmm, maybe the datafiles of Shard for evorts have to be updated?

But why would it function when the gadget handler tanked the first time?

Separate lua VMs, this is more likely an issue with the gadget handler being taken out interrupting the expected flow of events. Hence why shard started building once given a commander