Re: memory leak in asp 2.0
- From: "Aleks Kleyn" <Aleks_Kleyn@xxxxxxxxxxx>
- Date: Tue, 31 Jul 2007 22:16:50 -0400
I do not have recursion. The code is prety simple. At logon I open dataset and appropriate tableadapters and save them and few datatables in session. Some datatables I may fill on different pages. Some datatables I use on diferent tables to databind controls. May be dataadapter should be open for short time or control has hiden recursion.
Also it would be useful to know how much specific page gets in memory or when I leave it forever, so I can release it forever.
"Peter Bromberg [C# MVP]" <pbromberg@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:33459E2B-DCA6-4D79-982B-AD659623ED8F@xxxxxxxxxxxxxxxx
Aleks,
What you describe is not a normal operating condition and may very well be
caused by poorly written code (e.g, not closing connections, etc.)
Peter
--
Recursion: see Recursion
site: http://www.eggheadcafe.com
unBlog: http://petesbloggerama.blogspot.com
bogMetaFinder: http://www.blogmetafinder.com
"Aleks Kleyn" wrote:
I wrote application on asp.net 2.0 using dataset. One dataset I put in
session collection and other (which is small and common for other users) I
put in application. I expected that it will get some amount of memory,
however I expected that this amount of memory will be fixed and will depend
on number of user. When I put code in production I discovered that
aspnet_wp.exe increases memory which it uses. Each second 2meg. What may be
the reason. I expected that when I load new page, every variable that I use
in old page releases memory. How I can find where I did not release memory.
I call each time 'Page unload' when I load new page but never when I close
it.
.
- Follow-Ups:
- Re: memory leak in asp 2.0
- From: Kevin Spencer
- Re: memory leak in asp 2.0
- References:
- memory leak in asp 2.0
- From: Aleks Kleyn
- memory leak in asp 2.0
- Prev by Date: Re: Multi Tier Sample
- Next by Date: Re: Bypassing INamingContainer for server controls on page
- Previous by thread: memory leak in asp 2.0
- Next by thread: Re: memory leak in asp 2.0
- Index(es):
Relevant Pages
|