I, like probably 10s of 1000s of others, use an I2C Inertial measurement Unit (IMU) on the Pi. I might typically take 150 I2C readings per second. That would be left running for hours at a time. Perhaps 4 million error free I2C readings in a session. What language is this in? (I accept that it's pr...

At the moment relays are not inserted. There are about 20cm of I2C track and lots of 0.1u capacitors scattered around.

No, I have not seen that .....

I do:
var spawn = require('child_process').spawn,
cp=spawn('i2cget', ['-y', '1', iicAddr, 0x12, 'w']);

I can talk to my MCP23017s with the wiringPi and IC2-TOOLS but once every few thousand times it does not work and causes the application to crash (this is with IC2-TOOLS, I have not done a soak test with wiring-pi).

The IC2 module in node.js causes a segmentation fault quite quickly.

I'm not sure that i2cget was designed to be anything more than a convenient way to test that a I2C chip was functioning correctly during installation. Doesn't node.js have a proper implementation of I2C?

If I use the official node.js I2C module I get segmentation faults.

I am having problems with I2C. To control my heating system I need approx 24 inputs and 24 outputs so I have made a PCB with 3 off MCP23017 lots of relays, optical isolators etc. The MCP23017 has 16 IO pins and an IC2 interface. My language of choice is node.js, this has an I2C module which works so...

I have a similar problem in that if I use I2C my node.js code crashes with a segmentation fault.
If I use i2cget (part of i2c-tools) the code crashes after ~3000 calls to i2cget as a child process

Is i2c broken on Raspberry Pi?