I’m afraid I haven’t got any definite answers. Graham Dumpleton’s tips were most helpfull, but unfortunately he didn’t make an answer (just comments), so there is no way to accept his response. Although I still haven’t fully resolved the issue, here are some basic tips for other people having similar problems: Read Webfaction’s documentation: Reducing … Read more
I go with door #2: This is not a real leak. More specifically, it’s just related to garbage collection. Three clues: The path to GC root ends at FinalizerReference, which is closely related to GC. It basically handles calling the finalize() methods on objects that are eligible for GC — for which there is one … Read more
I had faced the same issue and (thanks to Stackoverflow) fixed it by changing MKMapType in viewWillDisappear and deallocating/setting its delegate to nil.As it still sends message to delegates. This is documented in MKMapViewDelegate Protocol Reference: Before releasing an MKMapView object for which you have set a delegate, remember to set that object’s delegate property … Read more
This blog post appears to descibe what you are seeing, and the proposed solution was to create an implementation of Stream that wraps another stream. The Dispose method of this wrapper class needs to release the wrapped stream, so that it can be garbage collected. Once the BitmapImage is initialised with this wrapper stream, the … Read more
second the valgrind… and I’ll add electric fence.
The main method for detecting memory leaks is heap profiling. Specifically, you’re looking for unexpected growth in the amount of resident (mostly heap) memory, either the maximum residency in the +RTS -s statistics output, or — more reliably — a characteristic “pyramid” shape over time in heap profile output generated with the +RTS -h<x> flags … Read more
Can there be memory leak in Java? The answer is that it depends on what kind of memory leak you are talking about. Classic C / C++ memory leaks occur when an application neglects to free or dispose an object when they are done with it, and it leaks. Cyclic references are a sub-case of … Read more
I tried this […] lazy var personalizedGreeting: String = { return self.name }() it seems there are no retain cycles Correct. The reason is that the immediately applied closure {}() is considered @noescape. It does not retain the captured self. For reference: Joe Groff’s tweet.
I never did find and answer to this. Instead, I would null the node on hide and restore it back on view. For intensive dynamic nodes/multiple nodes I created a hash map to store them in memory. This has sort of become a habit for me in javafx8 to dispose all graphics and reassign on … Read more