.NET and destructors!!!!!!!!!!!!!

**Jabberwocky** · 1 April 2006, 13:45

Just use Java and get your garbage collected.

**Francko** · 1 April 2006, 13:58

Originally posted by Jabberwocky

Just use Java and get your garbage collected.

Same as in .net. The garbage collector will decide when to call the destructor. At least, you can write one.

.Net! The best! The future!

**AtW** · 1 April 2006, 14:02

Originally posted by Francko

At least, you can write one.

Does not mean you should

**Cowboy Bob** · 1 April 2006, 17:01

Originally posted by Francko

Same as in .net. The garbage collector will decide when to call the destructor. At least, you can write one.

You can in Java too. You override the finalize() method from the Object class. Though as in .NET, the garbage collector has a mind of its own and will garbage collect when it feels like it.

**Fungus** · 1 April 2006, 18:37

Our garbage collector comes round once a week. We have to put recyclables in the green bin.

**mcquiggd** · 1 April 2006, 20:31

And you have to move your object references to the end of yer driveway or else theyll be left there for days....

Ok, I admit, its time to get out of IT...

**VectraMan** · 1 April 2006, 20:50

Originally posted by Fungus

Our garbage collector comes round once a week. We have to put recyclables in the green bin.

Except when they're on strike.

I think I want my objects destroyed when I bloody well tell them to be destroyed.

**AtW** · 2 April 2006, 09:15

Originally posted by VectraMan

I think I want my objects destroyed when I bloody well tell them to be destroyed.

You said it - I can agree with GC deciding when to collect garbage, however if I call GC.Collect() this means it MUST collect, or at least not to keep classes with destructors hanging for a long time - the funny thing is that happens only in SOME circumstances in .NET 1.1, but seems to happen full time in .NET 2.0

Originally posted by cswd

Make sure they implement IDisposable and stick them in using blocks.

Yes I started using IDisposable for a long time, but I also had destructor - this was the undoing as GC seems to have queued them for destruction in a separate thread that was taking AGES to execute under some circumstances that I managed to re-create.

Highly annoying memory "leak" was fixed by commenting out destructors, I mean this is BS! Can't always use "using" block since I need to have many objects that will self-destruct when needed.

**AtW** · 2 April 2006, 10:40

Originally posted by cswd

The object should have finished it's work when you've finished with it and released it for destruction. The only thing it should do is free the heap later (all stack stuff is freed during execution).

Which was exactly the problem - I had Dispose called for all objects, but they were not removed from heap because objects had consturctors, so GC in its wisdom thought to keep them around since it assumed that just because machine has got 2 GB of RAM its okay to eat 300 MB of it for no reason - crap GC design. If programmer explicitly calls GC.Collect() then GC should either collect garbage or new developer responsible for GC should be hired.

Originally posted by cswd

If that fails, stick 12Gb of memory in the machine (I've had to do this before!). Plenty of room for the GC to fill up.

I don't like solutions like this - this problem in GC was responsible for another strange memory leak that I had - starting at 300 MB but working its way to 1.5 GB until it run out of memory, effectively it seemed that GC stopped working

.NET and destructors!!!!!!!!!!!!!