Browse: Home / Windows Live Writer Can Bring a Beast of a Computer Down

Windows Live Writer Can Bring a Beast of a Computer Down

By on June 5, 2009

Time for a confession: for being a SaaS-fan and sticking to using Web applications whenever I can, there is one client app I really like: Windows Live Writer. Simply the Best Blog Editor.  Except you can’t work too long in it.  It gets this crazy idea that it should own my entire system and it starts eating memory. The image below is not at all unusual for WLW: 85% CPU usage (on a dual-core system) and 1.2G Memory.  Pretty pathetic.  Perhaps time I really follow my advice and move this last bit to the Cloud, too.

Posted in | Tagged , , , , | 5 Responses

LinkedIn Twitter Facebook
Publisher / Editor @ CloudAve and Enterprise Irregulars. Industry Observer, Blogger, Startup Advisor, Program Chair @ SVASE (Silicon Valley Association of Startup Entrepreneurs). In his "prior life" spent 15 years immersed in the business of Enterprise Software, at management positions with SAP, IBM, Deloitte, KPMG and the like.

5 responses to “Windows Live Writer Can Bring a Beast of a Computer Down”

  1. Robin Capper
    Robin Capper June 5, 2009 at 1:30 am |

    Or try BlogJet, which I use with a Mesh folder so can edit drafts on a couple of machines using local data/app but still cloud synced

  2. Evan Low
    Evan Low June 5, 2009 at 6:50 am |

    Let me know if you find an alternative to WLW.

    Web (Saas) or Programs (e.g. Openoffice) are available for both my notebook (Windows) and netbook (Linux). WLW is the only one that I use daily that is only available in Windows.

    Funny how after moving most of my processes to the web, I still have to contend with WLW and Firefox taking up most of my machine resources.

  3. Zoli Erdos
    Zoli Erdos June 5, 2009 at 8:52 am |

    I took this screen pic while editing the much longer Tank Man post, which includes 3 videos. I have no idea if the videos are the culprit, but I was simply unable to finish editing there, the entire system came to halt and I had to close WLW every 5 minutes or so.

    Then I pasted the html into our blog platform’s (Zoho)editor and finished the post easily.

  4. Brandon Turner [MSFT]
    Brandon Turner [MSFT] June 5, 2009 at 1:43 pm |

    Hello,

    I am one of the developers of Windows Live Writer. Since WLW uses Internet Explorer to render your blog post, and often times media like videos use 3rd parties(like Flash or Silverlight) there is a lot of places a bug can arise from. If you want to follow up on this issue send me (at wlw-team@microsoft.com) the wpost file (found in your ‘My Weblog Folder’ in your Documents folder) and I will see if I can reproduce the bad memory usage.

    Sorry for the bad experience!

  5. Zoli Erdos
    Zoli Erdos June 5, 2009 at 3:04 pm |

    Brandon,

    Thanks for your comment, I’m sending the file! :-)