I am new in this, did not use FileUp before and do not have expirience with this.
Found that FileUpEE for ASP/ASP.NET Version 5.1.2.58 has memory leak [we used profiler to find it]

This is simple code snipet that we are using to transfer file, that is leaking memory :

                using (FileUpEe fe = new FileUpEe())
                {
                    fe.TransferStage = saTransferStage.saWebServer;
                    fe.TransferFile(Context, filePath, fileServerUri);
                }

My question is , does version 5.1.2.58 have known memory leak issue ?
Do we need to use the latest version ?

SORRY for late answer.

Memory leak reason is :

USING statement will not RELEASE memory of new instance of FileUpEe component

Create WEB app and run next statement in loop [as in my app] and you will see memory leak immediately in windows performance monitor [check private bytes counter] or any memory tool..

I have simple web test app but could not figure out how to attach zip file on this post ?

But it is really loop around USING statement ,exactly as this :

for (int ii = 0; ii <10000; ii++)
{
       //memory leak is related with init new instance of FileUpEe
        //using statment will not release memory
         using (FileUpEe fe = new FileUpEe())
          {
               fe.TransferStage = saTransferStage.saWebServer;

                   //transfer will not cause memory leak, comment it
                  //fe.TransferFile(Context, incomingFileURL, fileServerUri);
           }
}