When working with handles and you don't register the addref/release behaviours for that class the compiler crash in as_builder.cpp at line 1152. Here is an example: Add an application function to the engine with the following declaration: "iStorage@ NewSubStorage(bstr ∈ name, bstr ∈ device)" Don't declare addref/release for iStorage class. When using the NewSubStorage function in a script the compiler crash during compilation. I think that the compiler should detect that the handle reference count functions are not declared and exit with a compilation error. Also, I don't know if the addref/release behaviour are necessary for classes registered with size zero (script cannot create objects of that class). I'm having all sorts of compilation crashes when using handles to objects from classes without addref/release so i guess it will be easy to reproduce the bug. If you don't I will send you a complete example.

This is exactly what I do: by default I register 2 callbacks that don’t do anything. The problem is that after that I may want to register my custom 2 handles for addref/release. The script engine doesn’t allow reregistering these handles again and exits with error. So maybe it is better to allow changing the behaviors (of course prior to compilation).

I'm encapsulating all the scripting system through interfaces so theoretically I can support multiple scripting languages at the same time. I registered the class with a call (like iScriptEngine::RegClass(const char *class_name, const int size)) and never bothered to add addref/release behaviors for the most classes since i've registered some default ones in RegClass function. After this call I want to add some real addref/release for some classes. But I cannot since the internal implementation of the RegClass added some dummy ones.

Anyway the problem is solved since I've included a parameter in the RegClass (const bool add_default_behavior = true). So I will set this param on false for classes with real addref/release.

This is not a problem for me anymore. A problem is the memory allocations made by the script runs. Now, I'm using multiple DLLs and one allocation in one lib space cannot be freed in another DLL. Having the angelscript statically linked to a dll and trying to delete an object (in Release when ref count reaches 0) in another dll cause heap corruption. The object is allocated by angelscript when entering the script scope (block) in script engine dll memory space, and deleted in another DLL that registered the class.

I've resolved this problem but it will be nice if I can hook my own allocation functions with the angel script. I can run my custom allocator and memory leak detection mechanism for scripts, too. But that is not a priority for me right now.

Thanks
Licu