Memcached crash on windows

Logs attached. From Sean:
For some reason we seem to be getting a message from the port for each character memcached writes to its output, which makes it pretty hard to read its output (per Dustin, this has been fixed), but it seems to be saying:

"FATAL: The engine does not support tap" but this is after the crash, and it's what it says when it gets a tap connection for a bucket that doesn't exist yet, a normal symptom after it restarts.

Prior to that, it exits with exit code 255, with no output whatsoever, four seconds after the last vbucket is set to active. My guess is it's running out of RAM or disk space or some external process is killing it.