. All the loaded dlls have to be located somewhere. There is also some structures allocated in each to keep things running. Something can be optimised for sure, but we need to be sure it is a good way to spend our timeRegards
Nick
memory release
Re: memory release
Sorry about the 20mb . All the loaded dlls have to be located somewhere. There is also some structures allocated in each to keep things running. Something can be optimised for sure, but we need to be sure it is a good way to spend our time
Regards
Nick
. All the loaded dlls have to be located somewhere. There is also some structures allocated in each to keep things running. Something can be optimised for sure, but we need to be sure it is a good way to spend our timeRegards
Nick
Re: memory release
Thats fine. As long as it releases everything on close. I know at one point, in version 3, at least, we had an issue when closing our application, which seems to no longer be an issue. We had an exception when using the X button to do with referecene counting.
Re: memory release
Yes everything is definitely released on exiting the application, independently were there leaks or not. This is because the native process is terminated and the memory pool is removed completely for reuse by the system. It is managed by Windows
Nick
Nick