Windows Live Messenger 2010 Problems...

[AnotherMuggle]

Is anyone else having problems with the latest version of Windows Live Messenger?

For some reason it is working very slowly. Dragging a message window around the desktop makes it stutter across the screen. The mouse cursor disappears when hovering over the client. Sometimes clicking the icons on the task bar will not bring messenger windows to focus.

I have tried a repair via Programs & Features (windows 7 64bit) and done an uninstall, re-download & re-installed. Same symptoms...I'm at a loss.

All other applications appear to be running just fine...no slowness and no unexpected behaviour. Avast Free and Malwarebytes seem happy that I am virus and malware free. The only other oddity of my computer is that a bunch of services seem to crash from time to time, I already have a thread open regarding this.

Cheers,
Tom

EDIT: I also just checked in Task Manager and WLM is consuming a lot of memory, 127,568K and somehow wasting CPU time at 22% usage. That's with one active chat. To put this into perpective, Firefox with 6 tabs and a bunch of Add-ons installed is using less memory and idles at 0% CPU.

[glc]

Can I suggest that you use a 3rd party messaging program such as Digsby or Pidgin to manage your IM accounts?

[Anomo]

Mine is working fine (fully updated) and I also have win 7 64-bit. So it must be your computer, not the program that there is something wrong with.

At least that is a start to the troubleshooting

[AnotherMuggle]

Thanks for the responses, I use Pidgin at work and will temporarily revert to it at home too. It's a very nice client but doesn't support a few of the features available in WLM. For now I can live without them!

I've done some more reading and investigation myself and discovered that the WLM problem appears to be related to Facebook. Google searches suggest users have seen similar issues, but I can't find anything specific to this build of WLM.

I can launch and use WLM trouble free until I browse to Facebook in Firefox (I've not tested so far with IE or otherwise) when WLM immediately starts eating resources. I believe (but could be wrong) that Facebook integration is a new feature for WLM and I'm slowly convincing myself there's a bug somewhere. I can literally watch the memory usage climb when I browse to Facebook which to me suggests there's a pretty nasty memory leak somewhere.

[AnotherMuggle]

I have connected Visual Studio 2008 debugger to msnmsgr.exe and the debug window is continually spammed with the following:

First-chance exception at 0x770bb727 in msnmsgr.exe: 0xE0000001: 0xe0000001.
First-chance exception at 0x770bb727 in msnmsgr.exe: 0xE0000001: 0xe0000001.
First-chance exception at 0x770bb727 in msnmsgr.exe: 0xE0000001: 0xe0000001.
The thread 'Win32 Thread' (0x7ec) has exited with code 0 (0x0).
First-chance exception at 0x770bb727 in msnmsgr.exe: 0xE0000001: 0xe0000001.
First-chance exception at 0x770bb727 in msnmsgr.exe: 0xE0000001: 0xe0000001.
First-chance exception at 0x770bb727 in msnmsgr.exe: 0xE0000001: 0xe0000001.
The thread 'Win32 Thread' (0xf2c) has exited with code 0 (0x0).