I have an iojs app that sends images over websockets (socket.io + ws module as client). As of iojs 1.5.1 this started maxing out the CPU instead of taking ~5%. I narrowed it down using the nightlies:
v1.5.1-nightly20150308fe36076c78 - 08-Mar-2015 02:20 - not affected
v1.5.1-nightly20150309030a92347d - 09-Mar-2015 17:30 - affected
Latest nightly is still affected.
strace shows hundreds of cacheflush calls in the affected builds but none in the unaffected builds.
cacheflush(0x34f1baa0, 0x34f1bae8, 0, 0x1, 0x34f1bacc) = 0
cacheflush(0x34f1bb40, 0x34f1bb70, 0, 0x1, 0x34f1bb5c) = 0
cacheflush(0x34f1bbc0, 0x34f1bc6c, 0, 0x1, 0x34f1bc48) = 0
cacheflush(0x34f1bcc0, 0x34f1bd08, 0, 0x1, 0x34f1bcec) = 0
cacheflush(0x34f1bd60, 0x34f1bdd4, 0, 0x1, 0x34f1bdb8) = 0
cacheflush(0x34f1be20, 0x34f1be94, 0, 0x1, 0x34f1be74) = 0
I have an iojs app that sends images over websockets (socket.io + ws module as client). As of iojs 1.5.1 this started maxing out the CPU instead of taking ~5%. I narrowed it down using the nightlies:
Latest nightly is still affected.
strace shows hundreds of cacheflush calls in the affected builds but none in the unaffected builds.