Yes I have run into garbage collector hiccups in Java. At the time I got around it by basically keeping a reference to the objects around when I was done with them, and then re-initialized them and re-used them as needed. So the garbage collector had nothing to do.
It was a little awkward but it worked great. I could get away with that because they were all fixed size.
I have to agree, the C# GC must be far more efficient, because with Java, especially on an android, when it hits you might lose a half-second (I know that sounds like a 'who cares', but it can cause grief)
Yes I have run into garbage collector hiccups in Java. At the time I got around it by basically keeping a reference to the objects around when I was done with them, and then re-initialized them and re-used them as needed. So the garbage collector had nothing to do.
It was a little awkward but it worked great. I could get away with that because they were all fixed size.
I've never yet had an issue with the GC with C#.
I have to agree, the C# GC must be far more efficient, because with Java, especially on an android, when it hits you might lose a half-second (I know that sounds like a 'who cares', but it can cause grief)