Currently, classes such as SocketEndPoint create a new CodeGenerator each time they're created which leads to yet another Assembly being loaded into memory. This is seriously wrong as Assemblies cannot be unloaded and thus creating new SocketEndPoints leads to leaking memory (unless the caller happens to know this implementation detail).
In the end default constructing an object should initialize it into a state which is desired whereas leaking memory is not desired...
Kittyfisto
commented
6 years ago
Currently, classes such as SocketEndPoint create a new CodeGenerator each time they're created which leads to yet another Assembly being loaded into memory. This is seriously wrong as Assemblies cannot be unloaded and thus creating new SocketEndPoints leads to leaking memory (unless the caller happens to know this implementation detail).
In the end default constructing an object should initialize it into a state which is desired whereas leaking memory is not desired...