Click here to Skip to main content
15,899,679 members

Comments by srastogi85 (Top 28 by date)

srastogi85 29-Mar-14 14:42pm View    
probably yes , but i thought someone in forum can guide me regarding possiblity , or some article where i can read about it
srastogi85 11-Oct-13 16:20pm View    
hi Mike ,
I see version of mscorelib as 2.0.50727.821,
I am currently using 2.0.50727.5472 , so this should inclide the fix, or i
should put this hotfix?
I think it includes from numbers i think
Thanks,
Shreyas
srastogi85 11-Oct-13 15:57pm View    
Hi Ron,
I understand , actually its a big enterprise application with using DTOs and objects from Infragistics , sorry cant post the code as its not possible wanted to have some idea how to debug or identify the issue.
Thanks
srastogi85 11-Oct-13 14:00pm View    
hi,

I tried to debug the issue using Debugdiag , it showed memory leak in below libs ,

these are the dlls where leak occurs , over i period time the leak for these dlls increases , leading to application crash, Please suggest what can be done.

I am using .NET framework 2.0 and my application is 32 bit.

mscorwks.dll is responsible for 121.05 MBytes worth of outstanding allocations. The following are the top 2 memory consuming functions:

mscorwks!EEVirtualAlloc+119: 120.69 MBytes worth of outstanding allocations.

mscorwks!DebuggerHeap::Alloc+2f: 284.07 KBytes worth of outstanding allocations. If this is unexpected, please contact the vendor of this module, Microsoft Corporation, for further assistance with this issue.

Warning WindowsCodecs.dll is responsible for 13.51 MBytes worth of outstanding allocations. The following are the top 2 memory consuming functions:

WindowsCodecs!WPF::ProcessHeapImpl::Alloc+16: 13.43 MBytes worth of outstanding allocations.

WindowsCodecs!zcalloc+1c: 86.67 KBytes worth of outstanding allocations. Thanks,

Shreyas
srastogi85 4-Oct-13 17:49pm View    
I didnt ignored Sergey , but couldnt get much info from it , nyways still looking for a solution