Crash when handling NFC events with Web IDE connected

I'm experiencing an issue with my new Puck when using it's NFC while connected to the Web IDE.

While the Web IDE is connected to the Puck, if my phone attempts to read the Puck as an NFC tag, after one or two successive reads, the Puck will appear to crash. It will no longer be seen as an NFC tag by the phone, and the Web IDE will either disconnect automatically, or realise it's disconnected after trying to issue a command. I won't be able to detect the tag, or see it again in the Web IDE, until the battery is reinserted.

If I upload the code, save it, disconnect the Web IDE (and lift the battery on the Puck) the NFC tag will be correctly identified - and does not crash, even after a many successive reads. (Uploading the code and scanning the Puck without lifting the battery often meant the tag was not detected)

My example code:

NRF.on('NFCon', () => print('Hello world!'));
NRF.nfcURL('https://www.google.com');

When the Web IDE is connected, I see a few print messages - but after 4 or 5 messages, the terminal output stops half way (Hello wo) - and the Puck crashes. I don't have any issues with other functions when connected to the IDE, such as printing a message when the button is pressed, or setting LEDs.

Has anyone else experienced issues with unreliable NFC behaviour when connected to the Web IDE?

Web IDE is running on a Macbook, using Chrome 58 and the internal Bluetooth.
Phone is a Nexus 5X, using Chrome to automatically open the URL in the NDEF message, and the "NFC Tools" app to read the Puck.
Puck is running the latest firmware available at the time of this post, 1V92.