The other day I posted a screen print of Windows Live Writer (the one and only client app I really like) eating up 85% of CPU and 1.2G memory. That’s pretty bad. Then I did a test: open up WLW fresh, open a draft post, then minimize WLW, and see how fast it would bring my system down without any activity. The result is this fascinating movie: about as exciting as watching wet paint dry.
I only stopped at 1.6G and 12 minutes because I got bored watching it.
So that’s the bad news. The good news is that it does not always happen, some weird coincidence of factors including a longer post with embedded videos and possibly with the Zemanta plugin installed. Even better news is that Brandon from the WLW team contacted my right after that post, and Andraz Tori, Zemanta’s CTO also jumped on the case.
So this may turn out to be a positive customer support story, after all…
Funny… I get less memory hogging and much more crashing. Zemanta crashes writer and writer crashes itself. That said it is a great application and, like you, it’s one of the few that remains on my machine…
Love Windows Live Writer. I compose in WLW, then upload to WordPress and do the Zemanta thing there — seems crazy but Zemanta definitely crashes WLW and the WordPress text composition box is not a patch of WLW.
I love WLW, never had a problem with it. some MS
products rule.