Note that a regular handle just protects the object from being collected by the GC. It does not protect the object from being moved by the GC.
You would need to create PinningHandle to prevent the GC from moving the object. The pinning handles are not good for GC though. When objects are pinned, the GC can't compact the heap and you get heap fragmentation. -Jan -----Original Message----- From: Discussion of the Rotor Shared Source CLI implementation [mailto:[EMAIL PROTECTED] On Behalf Of J. Redondo Sent: Sunday, April 17, 2005 1:02 AM To: DOTNET-ROTOR@DISCUSS.DEVELOP.COM Subject: Re: [DOTNET-ROTOR] GC Issues Thank you very much for your help. I will try the SetObjectReference(...) function and see what happens now during execution. Hope GC issues will be gone now. I think that the "this" issue you mentioned should not happen to me, because the "this" object is already stored in a HANDLETABLE, and I think that these objects are considered "safe" in these cases. =================================== This list is hosted by DevelopMentor(r) http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentorŪ http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
