@bdrung, the stack traces look awfully similar, but no looks like a different issue. bug #1094499 crashes a bit earlier in the code than this one, and looks like it's an invalid pgc pointer (at least, pgc=0x25 doesn't look like a proper memory address).
@bdrung, the stack traces look awfully similar, but no looks like a different issue. bug #1094499 crashes a bit earlier in the code than this one, and looks like it's an invalid pgc pointer (at least, pgc=0x25 doesn't look like a proper memory address).