ericsalo
ericsalo
Almost certainly just an annoyance instead of an actual bug. I will look into cleaning up these warnings.
Ugh. The trend in upb is actually to move towards more setjmp/longjmp, not less, because of how much simpler and more efficient it makes everything else.
I'm curious now as to whether this still breaks under Python/upb. I will investigate.
I have just patched the upb JSON parser to correctly handle float values very near the overflow limit, which is necessary but not sufficient for fixing this bug. The rest...
Impossible to determine whether this is a bug without a test case, would it be possible for you to post a simple one that reproduces the error?
The fix has just been submitted so imma close this.
This is about 99% Working-As-Intended. The thought occurs that *maybe* in a highly artificial loop like this one, we can recognize that the most recent arena allocation is being replaced...
Bouncing this over to @anandolee who knows way more about this stuff than I do.
A fix for this has been written, should be pushed tomorrow unless something unexpected happens.