You are reading a single comment by @jtq and its replies. Click here to read the full conversation.
  • Yeah - in my actual code I'm passing a complex JSON object that gets stringified for transmission over the serial port - the code above is a minimal test-case for Gordon, designed specifically to trigger the weird interpreter behaviour I'd noticed.

    The interpreter bug that causes the crash apparently depends only on how long the input to JSON.stringify() is (not what the actual type of the input is), so I simplified it down to a string for this test-case (and also because it's far easier to truncate a string to change its size during repeated testing than to start editing individual bytes out of complex JSON objects). ;-)

    But you can legitimately pass a plain string (or any primitive JS value) into JSON.stringify(), and it'll just pass the same value back, unmolested.


Avatar for jtq @jtq started