Lua crashing

[Retriever2]

I've been working on a level editor for a while, and between all the file IO and data structures and interface functions, I've put in a little over 2000 lines of lua, broken up into multiple module files that I load at runtime.

It's worked out pretty well, but a lot of times my application will crash when I exit it, or when lua throws an error - essentially when the lua engine terminates. A lot of the time, just a small code variation will change the crashing behavior. For example, adding a no-op line "local blah = 1 + 1", would prevent a particular function call from triggering an end-of-application crash.

Is there any particular magic to prevent this or is it known behavior, or am I over stressing the object? It seems like a cleanup issue of some kind because it (fortunately) doesn't crash during normal execution, just when lua terminates either on error or at end-of-application.

[xyzzy]

TL doesn't crash for me when i exit it (well a simplistic level doesn't, anyway)

[Retriever2]

It varies by build, and probably by computer because some people are complaining of the crashes. It's also crashing in my dev build right now, even if you don't do anything in it.

Windows reports exception 0xc0000005, memory access violation, maybe a dangling pointer somewhere.

[James]

The crashes are one reason I made the Lua+ object.

[Retriever2]

Is it out of beta yet?

[James]

Yes, but it has a few known bugs (they probably won't affect normal usage- I am going to fix them ASAP).

[vortex2]

Please send me an example program at vortex2 at gmail dot com and I will see if I can figure out what is going on... I have to admit that I am extremely busy so if I completely blow you off, it is nothing personal it is just that I didn't have time.

[Retriever2]

Thanks for the offer anyway. I understand being short on time. I've sent you my program because I have nothing smaller and it's nothing I can isolate. I hope crash data itself will be useful, because I don't expect trawling through code and events will be helpful in this case.