For some reason HFSExplorer runs out of memory in certain situations. It seems like there is a memory leak (some part of the program keeping references to data), or possibly a circular link situation (though that should have been taken care of).
Quick fix: Increase the memory ceiling for HFSExplorer (won't help in the case of circular link traversal).
Proper fix: Evaluate the allocation hot spots.
According to webbeddotpete at gmaildotcom, garbage collection doesn't clear any memory after such an OutOfMemoryError... meaning that some part of the program must collect references to previous allocations improperly.
Log in to post a comment.