I looked a bit into it and it seems to be unreleated to the patch. I sponsor the patch now, it fixes the problem at hand. A alternative approach would be to use "g_timeout_add()" in the destroy_engine() code and have a "really_destory_engine()" function that is run on the next gtk_main_loop and does the g_module_close() and g_free(engine). But your approach should be fine as well.
I looked a bit into it and it seems to be unreleated to the patch. I sponsor the patch now, it fixes the problem at hand. A alternative approach would be to use "g_timeout_add()" in the destroy_engine() code and have a "really_ destory_ engine( )" function that is run on the next gtk_main_loop and does the g_module_close() and g_free(engine). But your approach should be fine as well.
Thanks!
Michael