EldoS | Feel safer!

Software components for data protection, secure storage and transfer

SBSimpleSftp memory leaks

Posted: 09/09/2015 07:54:12
by Hans Heintz (Standard support level)
Joined: 09/03/2011
Posts: 3

I bought SecureBlackbox in september 2011.
For the first time i combined sending a file through SFTP using SBSimpleSftp with using FastMM4 for memory leak detection.
Sending one file results in a 350kb log from fastmm4 with memory leaks in which my code is never mentioned.
Can I simply assume the problem is with the version I have, simply download the new executable and install it over the old one and everything will work as before ( I only upload files with SFTP) and probably without the errors? Or is there some version specially known for stability?

Grtz, Hans

In case someone is interested a piece of the log file (which is basically repeated many times).

--------------------------------2015/9/9 8:06:38--------------------------------
A memory block has been leaked. The size is: 20

This block was allocated by thread 0x2EB4, and the stack trace (return addresses) at the time was:
403082 [system.pas][System][@GetMem][2648]
405E41 [system.pas][System][@NewAnsiString][12446]
4064F5 [system.pas][System][@LStrSetLength][13789]
6C1224 [..\Sources\SBCryptoProvWin32.pas][SBCryptoProvWin32][ProcessAlgorithm][8123]
6C1315 [..\Sources\SBCryptoProvWin32.pas][SBCryptoProvWin32][TElWin32ProviderInfo.RefreshSupportedAlgorithms][8148]
6C1111 [..\Sources\SBCryptoProvWin32.pas][SBCryptoProvWin32][TElWin32ProviderInfo.Refresh][7964]
6C1023 [..\Sources\SBCryptoProvWin32.pas][SBCryptoProvWin32][TElWin32ProviderInfo.Init][7862]
6BFEAF [..\Sources\SBCryptoProvWin32.pas][SBCryptoProvWin32][TElWin32CryptoProvider.AddProviderInfo][7288]
6BFF46 [..\Sources\SBCryptoProvWin32.pas][SBCryptoProvWin32][TElWin32CryptoProvider.RefreshProviderInfos][7315]
6BAAA3 [..\Sources\SBCryptoProvWin32.pas][SBCryptoProvWin32][TElWin32CryptoProvider.Init][3909]
70E310 [..\Sources\SBCryptoProv.pas][SBCryptoProv][TElCustomCryptoProvider.Create][1331]

The block is currently used for an object of class: Unknown

The allocation number is: 813875
Posted: 09/09/2015 08:35:26
by Ken Ivanov (Team)

Hi Hans,

Thank you for contacting us.

We can confirm that the allocations reported in the above log might not be released in the version of the product you are using; however, it is important to mention that these allocations all are one-off and remain alive for the lifetime of your application process (they keep information about algorithms supported by Win32 cryptoproviders). This, in turn, means that there is little sense in freeing the objects explicitly, as the corresponding memory is released by the operating system anyway when the application process shuts down.

We had added a mechanism for optional forceful release of permanent global objects at some stage in the past, but I can't say for sure if it is available in your version of the product (we would be able to tell that more specifically if we knew the exact build number of the version you are using).




Topic viewed 2094 times

Number of guests: 1, registered members: 0, in total hidden: 0


Back to top

As of July 15, 2016 EldoS business operates as a division of /n software, inc. For more information, please read the announcement.

Got it!