Reading zero bytes from i2c device causes Imp restart with memory error - expected behaviour?

Just for fun I tried this command but it restarted the IMP with a memory error.

`local ch1 = hardware.i2c89.read(MCP3424_ADDR << 1, "", 0)`

I know reading 0 bytes from an i2c device is probably nonsensical but should it cause a memory error?

This is a known bug which is was fixed in our tree back in august, but you won’t see it until release 34; memory error is where the impOS traps a bad memory access and reboots.

As you say, it’s a nonsensical thing to do so not something which requires an urgent deployment :slight_smile: