finalizer

问题 As I understand there are two camps concerning this question - the first one thinks that finalizer is a destructor specific to C#. So they think that these two things are the same. The second camp thinks that there's a slight difference - written in Wikipedia - "the term “destructor” is typically used to mean a deterministically-invoked cleanup, whereas a “finalizer” runs when the garbage collector says to run it." But let me clarify something for myself. Deterministically-invoked cleanup? In

问题 As a follow-up to this question, I have the following code: using System; using System.Runtime.InteropServices; namespace ConsoleApplication1 { class Program { class Child { public override string ToString() { return "I am a child!"; } ~Child() { Console.WriteLine("~Child called"); } } class Test { readonly object _child; readonly WeakReference _ref; readonly GCHandle _gch; // GCHandle is a value type, so it's safe public Test() { _child = new Child(); _ref = new WeakReference(_child); _gch =

问题 I'm not 100% clear on how an instance of class A can be defined to exist until after the last instance of class B is finalized. Or in other words, I'd like all B's to call close&dispose methods in A inside the B finalisation... and for that to happen before A itself is finalized. The scenario: A. I've got a managed wrapper for an unmanaged resource. For an analogy, lets call A a file system B. managed resources that refer to A, that in turn have requested an unmanaged resource via the A

问题 I have following Fortran code type t_octree integer :: max_num_point class(t_octree_node), pointer :: root => null() contains final :: DESTROY_OCTREE end type t_octree type t_octree_node real :: box(2,3) integer :: depth type(t_octree_node), pointer :: parent => null() type(t_octree_node), pointer :: children(:) => null() class(t_octree_leaf), pointer :: leaf => null() contains final :: CLEAN_NODE end type t_octree_node type, extends(t_octree_node) :: t_octree_leaf integer, allocatable :: id(

问题 I have following Fortran code type t_octree integer :: max_num_point class(t_octree_node), pointer :: root => null() contains final :: DESTROY_OCTREE end type t_octree type t_octree_node real :: box(2,3) integer :: depth type(t_octree_node), pointer :: parent => null() type(t_octree_node), pointer :: children(:) => null() class(t_octree_leaf), pointer :: leaf => null() contains final :: CLEAN_NODE end type t_octree_node type, extends(t_octree_node) :: t_octree_leaf integer, allocatable :: id(

问题 I have a class in C# where I want to close out some communication ports properly when my class is being disposed. However, the finalizer is never being called when I exit the program. Why is that? Am I doing something wrong? I am calling the dispose manually which goes through and closes all communications. This is not fired either. Here is the finalizer I am using: ~Power() { Dispose(false); } 回答1: The finalizer (which is what you're using here) is only called during the Finalization phase,

问题 Let's say I have created some resource class with a close() method for cleaning up the resource, and I want to override finalize() to free the resource (and print a warning) if someone has forgotten to call close(). How can this be done properly? Is it recommended only for native (JNI-allocated) resources? What happens if you use a reference to another object that has been finalized, from a finalizer? If there are cyclic dependencies I don't see how the garbage collector can prevent you from

问题 I just fail to understand why must one use Runtime.addShutdownHook. If you want to do some cleanup when the jvm exits, why not just overload the finalize method of the daemon class. What is the advantage of using shutdown hook over finalize method. Also there is a deprecated function runFinalizersOnExit. If I set it to false, I believe finalizers won't run. This contradicts the java guarantee that finalizers always run before garbage collections. 回答1: There is no guarantee that a finalizer

问题 In answering another question* on SO, and the subsequent comment discussion, I ran into a wall on a point that I'm not clear on. Correct me on any point where I'm astray... When the Garbage Collector collects an object, it calls that object's finalizer, on a separate thread (unless the finalizer has been suppressed, e.g. through a Dispose() method). While collecting, the GC suspends all threads except the thread that triggered the collection (background collection aside). What isn't clear:

问题 I'm trying to write a Java unit test that tests the effects of a call to a finalizer on an object. In order to be sure the finalizer gets called I'm using a WeakReference method I saw elsewhere on stackoverflow. My problem is that in this test the finalize method of TestFinalizer never gets called even though the WeakReference comes up null after just one iteration: public class FinalizerTest { private static class TestFinalizer { public static class Callback { public int NumFinalize = 0;