On 17 March 2010 10:16, Taylan Develioglu <tdevelio...@ebuddy.com> wrote:
> Here's a hs_err file after a crash I had yesterday. The list usually strips attachments; could you paste it? > It's a sigsegv in GCTaskThread. From the occupation in eden it looks > like it happened during a scavenge (ParNew). > > Ick. To roughly quote Dan Ingalls (who wrote several of the Smalltalk VMs, including their garbage collectors): "studying the behaviour of objects in the garbage collector is like studying frogs using a blender". I've tried modifying Squeak's GC algorithm, and that pretty much sums up my experiences! I'd expect seg faults in a GC thread to occur if, for some reason, pointers were getting corrupted on the stack or in the heap, or if a concurrency issue caused a read or write to the "old" location of an object after it had been moved. The GC is very sensitive to such things as it traces large portions of object memory, so may well stumble across corruption before any other thread does so. - Peter
