Comment 4 for bug 768576

A zombie process holds no resources except a process ID and an unread integer exit-value, so it's not that process per se, but if the parent process spins out of control, it could explain both how it hasn't read the exit value of the child, and how a computer could become sluggish. So, the zombie would be a side-effect too.

Fábio, can you log in from another computer (with ssh, perhaps) and run "ps xauww" to see a list of running processes, and "dmesg" to see what the kernel is doing?

Also, perhaps before it freezes, flip to the console (Ctrl-Alt-F1) and run the same commands. (Alt-F7 to go back.)

If it's "beam" that is eating CPU, please attach ~/.cache/desktop-couch/desktop-couchdb.log.1

If it's "desktopcouch-service" that is eating CPU, please attach these three:
~/.cache/desktop-couch/log/desktop-couch-migration.log
~/.cache/desktop-couch/log/desktop-couch-dbus.log
~/.cache/desktop-couch/log/desktop-couch-replication.log