bug found and fixed!

phew, it was a race condition having to do with the %500 process.nextTick() that
the iced core inserts. two pushes to the _inq were getting delivered out-of-order
since the first one got stuck going back to the bottom of the call stack and
the other got right through

solve the problem with a lock