garbage-collection

问题 I am using the default GC with 1.6.0_27-b07 (Sun's JRE) and because of this I am not able to detect an increase in memory with Runtime.getRuntime().freeMemory(). Can anyone shed a light on how to accomplish this? Do I have to use a different GC? Which one? The simple program below prints 0 for the memory allocated. :( :( :( import java.util.HashSet; import java.util.Set; public class MemoryUtils { private static Set<String> set = new HashSet<String>(); public static void main(String[] args) {

问题 I have built a ThreeJS app using the canvas renderer (due to project requirements) that I've run into a memory/garbage collection issue with. Part of the application logic creates a lot of meshes to achieve animations on segments of a flat 2d donut/ring. On each animation pass, we are removing all the previous meshes and generating new ones. When objects are removed from the scene, they're not deleted from memory but instead, moved to an array called __objectsRemoved. This is kept around

问题 I have an Android app that uses the SimpleFramework for XML serialization. The app runs fine on all real devices I have tested it on with no lags, but when run on the emulator, the garbage collector kicks in a runs for about about 3 minutes on each launch of the app. Here is what I have observed so far: Garbage collection kicks in just before serializing objects to XML It only happens before the first object is serialized and sent over the network, and does not happen for successive calls.

问题 I'm following the Dagger2 sample of TODO app but encounted with OutOfMemoryError: GC overhead limit exceeded. Along with it are 600+ warning likes: warning: Ignoring InnerClasses attribute for an anonymous inner class (org.eclipse.osgi.internal.baseadaptor.BaseStorage$StateSaver$1) that doesn't come with an associated EnclosingMethod attribute. This class was probably produced by a compiler that did not target the modern .class file format. The recommended solution is to recompile the class

问题 i use "-XX:+UseConcMarkSweepGC" in my application, and when Out Of Memory Error is close my application transform in weakly form of itself (in this time it logs "concurrent mode failure").In this form it can survive long time period, and that is a big trouble for me. I need to find way how to help my application to "die fast and easy". i googled this: "-XX:GCHeapFreeLimit=nnn where nnn is a number between 0 and 100 giving the minimum percentage of the heap that must be free after the GC. The

问题 C# has a unified type system in which all types, including primitive types inherit from object type. Java also has all of its classes inherited from object type. Quote from Thinking in java A singly rooted hierarchy makes it much easier to implement a garbage collector Does, unified type system or single rooted hierarchy help for doing Garbage collection and if so how ? 回答1: I think the main reason is it helps ensure that all objects have a Finalize method, thus enabling automatic

问题 A colleague of mine came across an article on codeproject over the weekend which describes the use of the auto_handle method. Given that the article was written in 2006, is that still the right way to handle deterministic disposal for things like file handles? We've tended to explicitly flush and close file handles and then delete the pointers and null them to be certain the GC has no excuse not to collect them (yes, we know we're super-paranoid). Using something like auto_handle looks like

问题 A colleague of mine came across an article on codeproject over the weekend which describes the use of the auto_handle method. Given that the article was written in 2006, is that still the right way to handle deterministic disposal for things like file handles? We've tended to explicitly flush and close file handles and then delete the pointers and null them to be certain the GC has no excuse not to collect them (yes, we know we're super-paranoid). Using something like auto_handle looks like

问题 public class A{ A a; public static void main(String args[]){ A b = new A();//new object created, obj1 b.a = new A();//new object created, obj2 b = null; //line 8 } } When line 8 is reached, obj1 is eligible for GC. Is obj2 also eligible for GC? 回答1: If you'd like to determine eligibility of an object for garbage collection, try to see if it is reachable from the root set. The root set are things like objects referenced from the call stack and global variables. In your example, the root set

问题 I have a function like the following: Public Function testFunction(ByVal input_string As String) As String Dim s As New StringBuilder() Dim c As Char For i As Integer = 0 To input_string.Length - 1 c = input_string.Chars(i) s.Append(c) Next Return s.ToString End Function but I want know if it's better to explicitly destroy any object, like this: Public Function testFunction(ByVal input_string As String) As String Dim s As New StringBuilder() Dim c As Char For i As Integer = 0 To input_string