Have you found any bugs in Native JSON implementations? [closed]

Answer 1

Chrome has a JavaScript implementation of JSON.stringify, instead of a native one, so it's actually slower than the JS one on JSON.org (although handles more edge cases).

http://code.google.com/p/chromium/issues/detail?id=22718

Answer 2

IE8 native JSON.parse bug causes stack overflow

Answer 3

Firefox 3.6 ignores the replacer return value in stringify.

bug report

test page

180 browser/platform combinations confirm bug