This is an unfortunate side-effect of MonoTouch (who is garbage collected) having to live in a reference counted world (ObjectiveC). There are a few pieces of information required to be able to understand what’s going on: For every managed object (derived from NSObject), there is a corresponding native object. For custom managed classes (derived from … Read more
The log message tells that GC was caused by Metaspace allocation failure. Metaspaces hold class metadata. They have appeared in Java 8 to replace PermGen. Here are some options to tune Metaspaces. You may want to set one or several of the following options: -XX:MetaspaceSize=100M Sets the size of the allocated class metadata space that will … Read more
From the very same page you just linked to: Some git commands may automatically run git gc; see the –auto flag below for details. If you know what you’re doing and all you want is to disable this behavior permanently without further considerations, just do: $ git config –global gc.auto 0
It’s also worth mentioning that, in the case of a subclass that has its own destructor, the parent destructor is not called automatically. You have to explicitly call parent::__destruct() from the subclass __destruct() method if the parent class does any required cleanup.
There’s a static reference to a singleton, so it won’t be eligible for garbage collection until the classloader is eligible for garbage collection. You can’t force any object to be garbage collected; you can request that the garbage collector runs with System.gc() but it’s only a request. If you really want to make a “singleton” … Read more
I do not see any difference between lock statement and Monitor.Enter call. Look more carefully. The first case copies the reference to a second local variable to ensure that it stays alive. Notice what the C# 3.0 spec says on the subject: A lock statement of the form “lock (x) …” where x is an … Read more
It’s significant, especially as fragmentation grows and the allocator has to hunt harder across larger heaps for the contiguous regions you request. Most performance-sensitive applications typically write their own fixed-size block allocators (eg, they ask the OS for memory 16MB at a time and then parcel it out in fixed blocks of 4kb, 16kb, etc) … Read more
I have shipped a non-trivial app written with Xamarin. Many others have as well. “Garbage collection” isn’t magic. If you create a reference that is attached to the root of your object graph and never detach it, it will not be collected. That’s not only true of Xamarin, but of C# on .NET, Java, etc. … Read more
Object A references object B. Object B references object A. Neither object A nor object B is referenced by any other object. That’s an island of isolation. Basically, an island of isolation is a group of objects that reference each other but they are not referenced by any active object in the application. Strictly speaking, … Read more
The way to close resources are context managers, aka the with statement: class Foo(object): def __init__(self): self.bar = None def __enter__(self): if self.bar != ‘open’: print ‘opening the bar’ self.bar=”open” return self # this is bound to the `as` part def close(self): if self.bar != ‘closed’: print ‘closing the bar’ self.bar=”close” def __exit__(self, *err): self.close() … Read more