There appears to be a bug/conflict (at least on my machine) with WinSCP that occurs when editing remote files using the internal editor. As soon as the internal editor opens the cpu usage goes berserk and as soon as I close the internal editor window the cpu usage drops to zero.
WinXP Pro SP2, latest updates
P4 HT 2.4 GHz, 2GB RAM
It happens with both SCP and SFTP and with both v3.7 and v3.8 beta. It could very well be some sort of conflict with another active program but I tried disabling as many programs as I could ... still happens. I reverted to using an external editor.
I did a search here but didn't find anything relevant (or maybe I missed it). Anyone else?