High CPU utilization on idle mount. about goofys

[kahing]

are there other processes reading from the mountpoint at the time? Also please upgrade to 0.0.5 as that fixes a deadlock issue (probably not related to your problem though)

[kahing]

and if you could attach a debugger and see what it was doing, that would be even better

[bedge]

At the time the connection was idle. All goofys clients had timed out and terminated
I have upgraded to 0.0.5 since this was reported.
Will be re-running tests with the newer version.

One thing I can say is that there are many concurrent threads accessing the mount point when the tests are running. So if this hasn't been tested with a high level of concurrency, that may be related.

If it happens again, it's in AWS, so I could get you access to the VM if you want to see first hand.

[bedge]

Have not been able to replicate with 0.0.5 running high volume.