Automatic checkout is enabled for my project. When I make new change to a file, a checkout attempt is made and if the pending changes window is open, I get the following error about 70% of the time:

"Attempted to read or write protected memory. This is often an indication that other memory is corrupt."

The file will check out, but it will not show up in the pending changes window, if I try to refresh the pending changes window I am greeted by this error again. If pending changes is not open, this error will not occur and if I close Visual Studio and open it again pending changes will load correctly. There is one other developer in the office this is affecting as well, but we can not find a rhyme or reason. Has anyone else experienced this?

Can you check to see if "Filter by Solution" (a toolbar button in the Pending Changes Window) is active? If it is can you see if turning it off alleviates the problem? There is a fix we made for the upcoming SP1 regarding Filter By Solution and memory access exceptions. This may be the same bug.

Thanks,
Ben Ryan