Re: DLL memory leaks
- Posted by jimcbrown (admin) Feb 05, 2014
- 1389 views
Okay, i see the problem.
But, a dll is made, becouse many differnt programs can use it, so you can't be sure if an other program still uses this dll.
Forcing an unload is not possible in this case.
Sort of. You can't force the OS to unload the shared library from all processes, however you can remove it from a particular process's memory address space - which in turn frees up memory for that process.
If the dll is only used by one program, then you have some other opportunities. You can move the dll to an .exe and use some kind of IPC.
If the loaded .exe exits all memory is cleanded up by the OperatingSystem.
Agreed. However, this can be more work than using a shared library, and may be ill-suited to certain types of functionality (e.g. where one has to pass around pointers in memory deal with inter-thread stuff or something).
On the other hand why should a "End User Programming with Hierarchical Objects for Robust Interpreted Applications" Language should handle this?
It shouldn't. The shared library unloading is dealt with in the operating system and in libdl.so
But memory leaks are a no no.
Maybe I'am to 'easyminded' but i prefer a 4.1x with memstructs over a 4.1.x with 'dll unloading'.
Just my 2 cent.
Andreas
Seconded.
