VS 2005 Won't Close Completely (50% CPU in Task Manager)

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Bruce - 16 Feb 2006 17:13 GMT

We are having a very consistent problem getting Visual Studio 2005 Pro
to close completely upon exiting. devenv.exe remains in the Task
Manager at 50% CPU usage. Opening and closing VS a second time adds
another instance at 50% CPU, which then brings the system to it's
knees. All of our developers have the same issue.

We are using VisualAssist X and Perforce plugins. Removing the
Perforce plugin seems to make the program go away, but this doesn't
seem to be typical for other Perforce users, including those at our
sister companies.

Anyone else see this or have any ideas what might be causing it or how
to track this down?

--Bruce

Reply to this Message

"Gary Chang[MSFT]" - 17 Feb 2006 05:39 GMT

Hi Bruce,

>We are using VisualAssist X and Perforce plugins. Removing
>thePerforce plugin seems to make the program go away, but
>this doesn't seem to be typical for other Perforce users, including
>those at oursister companies.

We haven't experienced any similar problems in our machines(no Perforce
plugins). It appears the Perforce plugins as well as something else in your
machines messed up with Visual Studio 2005, such as some anti-virus
softwares or tthe firewall system.

I suggest you can also contact the Perforce Support Services for this issue.

Thanks!

Best regards,

Gary Chang
Microsoft Community Support
======================================================
PLEASE NOTE the newsgroup SECURE CODE and PASSWORD will be updated at 9:00
AM PST, February 14, 2006. Please complete a re-registration process by
entering the secure code mmpng06 when prompted. Once you have entered the
secure code mmpng06, you will be able to update your profile and access the
partner newsgroups.
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================

Reply to this Message

Bruce - 17 Mar 2006 17:25 GMT

I have contacted Perforce support, and they are reporting the following:

"Our developers have investigated it and determined that it's a
result of Visual Studio failing to uninitialize P4SCC when it closes the
solution. This apparently then causes problems within the Qt event loop and
leads to hangs and/or crashes. Our developers haven't yet been able to come
up with a fix for this, since without the "uninitialize" call there's no way
for P4SCC to know when it's appropriate to clean itself up."

"Noted in the developers notes is that Visual Studio is not properly
UnInitializing the P4SCC. Effectively it initializes us 4 times, but only
UnInitializes us 3 times before shutting down. According to the spec the IDE
is responsible for cleaning up after itself."

How can I get a proper response from Microsoft on this, or find out if there
is a hotfix available that addresses this?

--Bruce

> We haven't experienced any similar problems in our machines(no Perforce
> plugins). It appears the Perforce plugins as well as something else in your
> machines messed up with Visual Studio 2005, such as some anti-virus
> softwares or tthe firewall system.
>
> I suggest you can also contact the Perforce Support Services for this issue.

Reply to this Message

VS 2005 Won't Close Completely (50% CPU in Task Manager)

Free Magazines