I'm into the final stages of development on my project so I thought i'd run it through paul nettle's memory manager (www.fluidstudios.com) and it got very annoyed with angelscript (currently working with 1.10.1WIP1). I will resolve the memory leaks on my end, I just thought it was worth mentioning to whom it may concern. :)

It is free and you just plug it in somewhere convenient like as_config.h and recompile. it doesn't actually optimize memory allocation by partitioning of small sections from a few large allocations - rather it works a lot like boundschecker to veryify that every single byte allocated has been freed & can even tell you when you are allocating blocks bigger than is actually needed. The mmgr complains some 20 times if I

I plugged in Paul's memory manager in the library and gave it a run. I didn't find any memory leaks, but there are a few places where AngelScript apparently deletes memory that it never allocated. I'm currently tracking these down.

The first one I found was not in AngelScript but in MSVC++'s std::string's destructor.

Good to know. ...i'm embarassed to say that, yes, i was deleting it. I guess I didn't read the doccos closely enough. That was the source of the problems. Why isn't the destructor protected or private?