By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,009 Members | 2,866 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,009 IT Pros & Developers. It's quick & easy.

"out" parameter and memory leak?

P: n/a
Hi Group,

I have written a window service wtih SAP.NET Connector which is to
fulfil request from SAP client. SAP client will call a function exposed by
my window service that has a big "out" parameter. That "out" parameter is of
class SAPTable, you can regard that as DataTable.

As everytime SAP client issue request to my window service, it will
connect to oracle and do some searching and return the result in a SAPTable.
I did a volume test by issuing 10,000 request and observed the memory usage
of the window services jumping from 20mb to 800mb.

I know reading the memory usage from Task Manager is not an accurate
method to judge the footprint of any .NET program. But isn't it my app got
memory leak? is it becoz of the jumbo "out" parameter which i has no way to
free it?

Please advise.

Alex
Nov 16 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Hi Alex:

You might want to try the CLR Profiler to see who / where / when is
allocating memory.

How To: Use CLR Profiler
http://msdn.microsoft.com/library/de...nethowto13.asp

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Tue, 2 Nov 2004 07:08:06 +0800, "Alex Chan"
<Ga********@hotmail.com> wrote:
Hi Group,

I have written a window service wtih SAP.NET Connector which is to
fulfil request from SAP client. SAP client will call a function exposed by
my window service that has a big "out" parameter. That "out" parameter is of
class SAPTable, you can regard that as DataTable.

As everytime SAP client issue request to my window service, it will
connect to oracle and do some searching and return the result in a SAPTable.
I did a volume test by issuing 10,000 request and observed the memory usage
of the window services jumping from 20mb to 800mb.

I know reading the memory usage from Task Manager is not an accurate
method to judge the footprint of any .NET program. But isn't it my app got
memory leak? is it becoz of the jumbo "out" parameter which i has no way to
free it?

Please advise.

Alex


Nov 16 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.