Im finding a strange possible memory leak when using in/out parameters on the Client side.
I include a parameter called “User” which is a RO complextype with in/out parameters.
The parameter is passed as a already created object, server sees it, process it, returns, all good. If server is shutdown FASTMM4 doesnt return any memory leak. Good stuff.
Client receives message and destroys the class. Client is shut down and memory leak is reported of the same class just got destroyed.
I’m attaching the SessionTypes sample with some modifications to reproduce the issue.
Just open server, open client, login/logout, shutdown client. See the memory leak report on screen.
(Sent via support email)