Search found 5 matches

by shan
Thu Jul 27, 2006 12:47 pm
Forum: Using .NET Memory Profiler
Topic: memory not recovering
Replies: 5
Views: 11824

i am using ado.net for the connection in the application ,so i think no problem with unmanaged resources. see even if i use gc.collect() one time, then also it recovers all the memory in first run or in second run ,not necessarily to use waitforpendingfinalizers() for collection ,what i wrote in my ...
by shan
Wed Jul 26, 2006 3:31 pm
Forum: Using .NET Memory Profiler
Topic: memory not recovering
Replies: 5
Views: 11824

new behavior with application

i have added gc.collect() then gc.waitforpendingfinalizers() and then gc.collect() in my pageunload event .Now when i run my application,in the first go click( asp button, for fetching data from server) the memory goes up and doesnt recover on page unload ,but on the second go click (same button) t...
by shan
Wed Jul 26, 2006 12:45 pm
Forum: Using .NET Memory Profiler
Topic: memory not recovering
Replies: 5
Views: 11824

need ur help Andreas Suurkuusk

hi andreas
i need ur help
please reply this problem
i am much puzzled about this problem
just give me few hints
waiting ur answer
by shan
Tue Jul 25, 2006 1:22 pm
Forum: Using .NET Memory Profiler
Topic: memory not recovering
Replies: 5
Views: 11824

memory not recovering

hi i need ur help my application is a simple web application which fetch data on the users request . when i run my application with the profiler , the follwoing statistics it shows 1) in task manager memory is 261 mb 2) in the profiler (physical memory) is 166 ( with profiler 261) private 147 mb man...
by shan
Mon Jul 24, 2006 9:06 am
Forum: Using .NET Memory Profiler
Topic: reinstalling the profiler
Replies: 1
Views: 7275

reinstalling the profiler

hi my installed memory profiler has been expired .i want install the same trial version software again ,can u tell how i can use the same thing again. actully after finding this forum ,i really got to know how to use this correctly . i know there will be some registry issue involved in this but plea...