Segmentation fault with yajl2 backend about ijson HOT 3 CLOSED

@avercau thans for reporting this.

I'm a bit confused: which backend was giving you errors: yajl2 or yajl2_c? They are two different backends, so we should clarify which one was causing issues. And obviously there's also very little I can do without further information.

However, assuming the issue is with the yajl2_c backend, I can venture that you might have been hitting the issue described in #66. That also occurred seemingly randomly, making it hard to reproduce (you can read the full issue to understand the context better). The good news is that I did push a fix for that (see the bug report for that, it's also mentioned in the CHANGELOG), although the original reporter never bothered responding whether the fix worked for them. Could you give that a try? The fix is only on the master branch of this repo, as I haven't released a new version of ijson to PyPI that contains it yet. That would be valuable information.

from ijson.

@avercau can you please provide some feedback on this? If this is a duplicate I'd like to flag it as such and close the issue.

from ijson.

Closing due to inactivity, hopefully it's a duplicate of #66.

from ijson.