[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

microsoft.public.dotnet.framework.aspnet.webservices

webservice behavior hogging memory.

(Gaz)

1/21/2003 10:16:00 PM

I have a big memory problem using the webservice behaviour.

I have a web page that uses the webservice behavior to call a c#
webservice function. As soon as the page is displayed the webservice
is called. The problem is that when I refresh the page the
IEXPLORE.EXE process consumes another 1meg of memory. My app refreshes
the screen regularly and so will therefore encounter major problems.

I know that the webservice behavior is causing this problem because if
I take out my webservice code ie; calls to useService() and
callService(), then I don't get the memory leak.

I have noticed that if I minimize and restore the IE window all the
built up memory allocation is cleared. Madness!

I've just looked at the webservice behavior pages on
msdn.microsoft.com and the webservice behavior is no longer supported.
This is great.

Has anybody got any ideas?

Gaz.
3 Answers

Mark Pearce

1/16/2003 2:57:00 PM

0

Hi Gaz,

What you're seeing is the memory allocation (the working set) rather than
actual memory usage - hence the minimize/restore behaviour. You can reduce
the working set programmatically from within your web service if you wish.
See:
http://tinyur...

Does this trick affect performance?
http://tinyur...

Hope this helps,

Mark

"Gaz" <oopaevah@yahoo.co.uk> wrote in message
news:76ee1253.0301160208.ce5022e@posting.google.com...
I have a big memory problem using the webservice behaviour.

I have a web page that uses the webservice behavior to call a c#
webservice function. As soon as the page is displayed the webservice
is called. The problem is that when I refresh the page the
IEXPLORE.EXE process consumes another 1meg of memory. My app refreshes
the screen regularly and so will therefore encounter major problems.

I know that the webservice behavior is causing this problem because if
I take out my webservice code ie; calls to useService() and
callService(), then I don't get the memory leak.

I have noticed that if I minimize and restore the IE window all the
built up memory allocation is cleared. Madness!

I've just looked at the webservice behavior pages on
msdn.microsoft.com and the webservice behavior is no longer supported.
This is great.

Has anybody got any ideas?

Gaz.

Mark Pearce

1/17/2003 1:00:00 AM

0

Hi Gaz,

Okay, I see what you're getting at now. It shouldn't cause resource problems
on the client because the memory is only being allocated, not used. If
another app needs that allocated memory, it should be able to take it away
from Explorer quite happily.

That's my understanding, at least. I'm not an expert on this subject!

Regards,

Mark

"Gaz" <oopaevah@yahoo.co.uk> wrote in message
news:76ee1253.0301161202.3a8b18e3@posting.google.com...
I'm not sure I explained the problem well. The memory is being gobbled
up on the client not on the server. The IEXPLORER.EXE process on the
client grabs an extra meg or so whenever I refresh a page which is
using the webservice behaviour. If I remove the call to the webservice
from the client page then the IEXPLORER.EXE behaves itself.

This causes resource problems on the client very quickly. The server,
where the webservice is hosted, is not relevant.

If what you said is still relevant could you explain in more detail?

> Hi Gaz,
>
> What you're seeing is the memory allocation (the working set) rather than
> actual memory usage - hence the minimize/restore behaviour. You can reduce
> the working set programmatically from within your web service if you wish.
> See:
> http://tinyur...
>
> Does this trick affect performance?
> http://tinyur...
>
> Hope this helps,
>
> Mark
>
> "Gaz" <oopaevah@yahoo.co.uk> wrote in message
> news:76ee1253.0301160208.ce5022e@posting.google.com...
> I have a big memory problem using the webservice behaviour.
>
> I have a web page that uses the webservice behavior to call a c#
> webservice function. As soon as the page is displayed the webservice
> is called. The problem is that when I refresh the page the
> IEXPLORE.EXE process consumes another 1meg of memory. My app refreshes
> the screen regularly and so will therefore encounter major problems.
>
> I know that the webservice behavior is causing this problem because if
> I take out my webservice code ie; calls to useService() and
> callService(), then I don't get the memory leak.
>
> I have noticed that if I minimize and restore the IE window all the
> built up memory allocation is cleared. Madness!
>
> I've just looked at the webservice behavior pages on
> msdn.microsoft.com and the webservice behavior is no longer supported.
> This is great.
>
> Has anybody got any ideas?
>
> Gaz.

(Gaz)

1/21/2003 10:16:00 PM

0

I'm not sure I explained the problem well. The memory is being gobbled
up on the client not on the server. The IEXPLORER.EXE process on the
client grabs an extra meg or so whenever I refresh a page which is
using the webservice behaviour. If I remove the call to the webservice
from the client page then the IEXPLORER.EXE behaves itself.

This causes resource problems on the client very quickly. The server,
where the webservice is hosted, is not relevant.

If what you said is still relevant could you explain in more detail?

> Hi Gaz,
>
> What you're seeing is the memory allocation (the working set) rather than
> actual memory usage - hence the minimize/restore behaviour. You can reduce
> the working set programmatically from within your web service if you wish.
> See:
> http://tinyur...
>
> Does this trick affect performance?
> http://tinyur...
>
> Hope this helps,
>
> Mark
>
> "Gaz" <oopaevah@yahoo.co.uk> wrote in message
> news:76ee1253.0301160208.ce5022e@posting.google.com...
> I have a big memory problem using the webservice behaviour.
>
> I have a web page that uses the webservice behavior to call a c#
> webservice function. As soon as the page is displayed the webservice
> is called. The problem is that when I refresh the page the
> IEXPLORE.EXE process consumes another 1meg of memory. My app refreshes
> the screen regularly and so will therefore encounter major problems.
>
> I know that the webservice behavior is causing this problem because if
> I take out my webservice code ie; calls to useService() and
> callService(), then I don't get the memory leak.
>
> I have noticed that if I minimize and restore the IE window all the
> built up memory allocation is cleared. Madness!
>
> I've just looked at the webservice behavior pages on
> msdn.microsoft.com and the webservice behavior is no longer supported.
> This is great.
>
> Has anybody got any ideas?
>
> Gaz.