Comment 2 for bug 394337

Hi, I've been having the same problems. Exactly the same problems.
I am running on [Ubuntu 9.04 - Jaunty Jackalope @ 64-bit].
My debug log about when do eats all cpu is attached below. I have not been able to catch a debug log of do when it crashes randomly, but since now I am always running do in a terminal with the debug flag, so I guess I will have the log as soon as do crashes again.

In summary, the debug log shows nothing alarming (only info lines and debug lines) but a [Warn] line each time I try to run something.

Very important: Do doesn't show up graphically as of startup time (this is when I get the 100% cpu usage).
If I close it and open it then Do works as expected.