EldoS | Feel safer!

Software components for data protection, secure storage and transfer

Memory Leak?

Posted: 04/16/2012 20:58:22
by Lam Soon Kin (Basic support level)
Joined: 04/16/2012
Posts: 6

Unfortunately, calling GC.Collect() does not solve the problem, neither using SignFiles method nor Sign method.

In .NETCF Remote Performance Monitor, it shows that "Manage byte in use after GC" is stable, while "GC heap" shows increasing trend.

A trace to call stack shows the "OutOfMemoryException" comes from

SecureBlackbox.dll!SBUtils.__Global.SetLength(ref byte[] aBytes = null, int aLength = 65536) + 0x1e bytes

This occurs in both SignFiles and Sign methods.
Posted: 04/17/2012 04:41:47
by Eugene Mayevski (Team)

SetLength() function allocates a managed array of bytes, which should be garbage-collected later. If GC doesn't work properly, there's nothing we can do about this.

Sincerely yours
Eugene Mayevski
Posted: 04/17/2012 05:40:40
by Eugene Mayevski (Team)

As we couldn't reproduce any of your issues, I've moved the question to the helpdesk for further investigation.

Sincerely yours
Eugene Mayevski



Topic viewed 2814 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!