Click here to Skip to main content
14,734,309 members

Comments by Anshul Mehra (Top 4 by date)

Anshul Mehra 7-Mar-13 21:17pm View
   
Yes the memory would still be leaking because the above release handler fn() only takes care of Handlers with closure, something like this

element.onevent=function(){..}.

The original post and discussion thread for the same is at
Javascript memory leak cleanup in window unload
Anshul Mehra 1-Feb-12 9:06am View
   
Javascript Memory leak has been confirmed by using "Drip" a JavaScript Leak Detector

I tried a solution
IntPtr pHandle = GetCurrentProcess();
SetProcessWorkingSetSize(pHandle, -1, -1);
But it would bring down the WorkingSet, But the Privatebytes still keeps spiking until it reaches out of memory and the app crashes.
Anshul Mehra 1-Feb-12 9:05am View
   
Deleted
Javascript Memory leak has been confirmed by using "Drip" a JavaScript Leak Detector

I tried a solution
IntPtr pHandle = GetCurrentProcess();
SetProcessWorkingSetSize(pHandle, -1, -1);
But it would bring down the WorkingSet, But the Privatebytes still keeps spiking until it reaches out of memory and the app crashes.
Anshul Mehra 1-Feb-12 9:04am View
   
Deleted
Javascript Memory leak has been confirmed by using "Drip" a JavaScript Leak Detector

I tried a solution
Collapse | Copy Code
IntPtr pHandle = GetCurrentProcess();
SetProcessWorkingSetSize(pHandle, -1, -1);
But it would bring down the WorkingSet, But the Privatebytes still keeps spiking until it reaches out of memory and the app crashes.