SKU, a member from another board reported to me an issue when a DLL is injected with the flag mustBeDisposed set to false.
In this case, the DLL must stay alive within the remote process, even if the instance of MemorySharp that injected the library is disposed, but it appears this is not the case.
The issue occurs here, where the parameter is never used.
public InjectedModule Inject(string path, bool mustBeDisposed = true)
// Injects the module
var module = InjectedModule.InternalInject(MemorySharp, path);
// Add the module in the list
// Return the module
I will fix this issue as soon as possible.