Script hook v .net crash on exit9/25/2023 ![]() Perhaps no use in your cirsumstance but that's my story. I was probably not marshaling my COM API calls properly or whatever.īut it seems that shutting the app down and restarting it was releasing the memory (along with the leaks) and letting it start afresh. Application 2 would then start application 1 back up.Īnd so on and so on, until all the work got done! Messy and frustrating but ended up working quite beautifully :) I'm sure there's a much much much better way of doing this. After so long application 1 would terminate itself but shell application 2 just before. Net application (application 2) which started up the crashing one (application 1). The way I resolved it was by writing another. This was causing some kind of memory leak, presumably in my application's workspace. Turns out it was because I was using a bunch of API calls and I was calling them very frequently. ![]() ![]() It wrote a log every time it entered and exited a routine so I could see exactly what it had done. I'd leave it running all night hoping to find it having done all my work by the morning. Add NativeUI.dll your references in Visual Studio just like you did with ScriptHookDotNet. Net application which was performing keystroke emulation on other applications. After installing ScriptHookVDotNet, copy NativeUI.dll to your scripts/ folder. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |