I'm not sure if this is a regression of the fix to issue #156, or if it's a new bug. For now, I've written up the description in a new comment on issue #156 (see #156 (comment)), because it seems very likely that this is a regression of the older bug. But if that's wrong, then I guess there's a shiny new seg fault instead.
Hope this helps, and please let me know if there's some better procedure I should have followed.