Python’s standard reference counting mechanism cannot free cycles, so the structure in your example would leak. The supplemental garbage collection facility, however, is enabled by default and should be able to free that structure, if none of its components are reachable from the outside anymore and they do not have __del__() methods. If they do, … Read more
What you are seeing is a known bug in iOS 5.1 and is being discussed in the iOS Developer Forums as such. You can find the relevant thread by searching in the forums for “strdup”. See the thread titled “Elements App Memory Leak”. Search for the post from an Apple employee.
I was able to reproduce the issue you are observing. It is clearly a flaw in the Channels library IMHO. Here is my repro: using System; using System.Diagnostics; using System.Threading; using System.Threading.Channels; using System.Threading.Tasks; using System.Threading.Tasks.Dataflow; public static class Program { public static async Task Main() { var channel = Channel.CreateUnbounded<int>(); var bufferBlock = new … Read more
Well, I found it. It IS a bug in the framework and to work around it you add a call to UpdateLayout. Using statement can be changed to the following to provide a fix; Using XPSItem As New Windows.Xps.Packaging.XpsDocument(PathToTestXps, System.IO.FileAccess.Read) Dim FixedDocSequence As Windows.Documents.FixedDocumentSequence Dim DocPager As Windows.Documents.DocumentPaginator FixedDocSequence = XPSItem.GetFixedDocumentSequence DocPager = FixedDocSequence.DocumentPaginator DocPager.ComputePageCount() … Read more
Ahhh got you. Now I understand what you mean. You set the Content to null and so you kill the compelte ListBox but still the ItemsSource binds to List and so ListBox memory is not completely released. That is unfortunately a well known issue and also well documented on MSDN. If you are not binding … Read more
I’m sure this is a duplicate, but I’ll answer it anyway: If you are viewing Task Manager size, it will give you the size of the process. If there is no “pressure” (your system has plenty of memory available, and no process is being starved), it makes no sense to reduce a process’ virtual memory … Read more
Most of the modern OS always reclaim back all memory they allocated to a program(process). The OS doesn’t really understand if your program leaked memory it merely takes back what it allocatted. But there are bigger issues at hand than just the memory loss: Note that if the destructor of the object whos delete needs … Read more
Try adding [webView loadHTMLString: @”” baseURL: nil]; right before you release the webview. For a leak in 4.2.1 relating to displaying a PDF in a UIWebView this solves most of the leak problems for me.
To get rid of compilation error in Joe H’s answer: sk_SSL_COMP_free(SSL_COMP_get_compression_methods());
I found that if you tell it to check memory automatically after the program terminates, it allows all the static objects to be accounted for. I was using log4cxx and boost which do a lot of allocations in static blocks, this fixed my “false positives”… Add the following line, instead of invoking _CrtDumpMemoryLeaks, somewhere in … Read more