slavapestov/factor — comment on commit c536c84c13686c2329baaca883f6b3a851cd6e74
File:  line 0
By jckarter:

It's getting into a memory fault loop because something (probably the exception handling crap) is trying to call `namestack`, which amounts to `0 context-object { vector } declare clone`. Since it's hitting the safepoint in `set-context-object`, `0 context-object` returns `f`, and the subsequent `vector` declaration causes `clone` to compile down into invalid memory accesses. The memory fault handler then tries to raise another error for the segfault and the cycle starts again.