dexplore.exe from VS2005 takes a lot of memory to run
Hi,
Installed VS2005 professional (Release), and when I run MSDN library for Visual 2005, it takes above 200mb on start - dexplore.exe takes that abount of physical memory. Also, the same problem happens with VS2005 itself - it takes more than 200mb while it starts.
If I will start another VS2005 instance - it will take 200mb too, and thats a problem for add-ins development.
Please, let me know, is there any way to fix this issue.
Few lines from the about box:
Microsoft Visual Studio 2005
Version 8.0.50727.42 (RTM.050727-4200)
Microsoft .NET Framework
Version 2.0.50727
Installed Edition: Enterprise
VS and Dexplore have a few components written in .NET. With all the GC logic, the memory reported in task manager can be a little off. One way to get a more acurate picture is to minimize (and then maximize) the Document Explore and VS to see how much memory drop does it result in. Mimizing forces the app to free up unused pages. I would be interested in knowing if the number still stays at 200 MB (especially for dexplore.exe).
--
Regards,
Saurabh
Hello,
I have the same problem - dexplore.exe virtual size is 250MB (before I even use it for anything).
Devenv.exe virtual size is 335MB, but I could understand that considering IntelliSense etc
Minimising and Maximising both has no effect
Any advice greatly appreciated, my PC really runs slow with VS2005
Thanks,
Mike
I had similar problems.
Problem behaviour:
I was working in VS2005 for a few hours then at some process started to use all the CPU. When I looked at the Task Manager it was dexplore.exe that was using 99% of the CPU. Its memory usage was 23,352KB (not as much as mentioned above). I stopped VS2005 and all other running appliations but dexplore.exe was still running in the background eating all the processing time.
I think it is unexceptable for a backround appliation to use up all the CPU time. It is not even running at a lower priority.
Questions:
Are there any service packs to fix this? What is dexplore.exe and its purpose? Killing the task will solve the problem temporarily.
Sorry to say but I am running the VS2005 SP1 Beta (from Microsoft Connect Beta Program) and the problem occurs here too, after about an hour cpu usage is maxed out, I don't notice it at first because on the dual-core system it is actually using 50% (100% of one of the processors).
It is quite frustrating closing down VS and restarting it to get it behaving again. dexplore.exe is the Visual Studio Document Explorer (MSDN/Help Viewer), I am also getting crash messages saying that Document Explorer has had to close down and do I want to restart it.
Any ideas MS?
Using VS 2005, dexplore.exe is running in the background and consumes 100% cpu time (on a dual cpu machine) and is using 29 MB. Is there a fix?
Thank You
Michael
Michael,
Is dexplore responsive while it uses the CPU? Are you running into this issu on 32 or 64 bit machine?
--
Regards,
Saurabh
I noticed on my Windows XP SP2 computer, with Visual Studio 2005 Standard, dexplore was running with 50% CPU usage even after I exited Visual Studio and the help viewer.
This thing just bit me as well. About 23MB and using 100% of the processor even after I shut down VS2500 and the document explorer.
The machine contains two 1Ghz Pentium III running 32 Bit XP Pro. 1GB memory.
I guess that I do not how to judge if dexplore is responsive. The machine remained responsive, and VS 2005 Help remained responsive.
Unfortunately I have several tasks that are keeping me from continuing the VS work at this time.
Saurabh, Thank you for helping me with this problem.
Regards
Michael
P.S. The 100% CPU Utilization is 100% of one of the two CPU.
i'm having the same issue. no one has any ideas?
18 hours after I quit VStudio 2005 and all other Microsoft development tools, dexplore.exe was still using 50% of my CPU. My system is running all OS and development tool updates.
It seems to me that, since dexplore.exe is a support process for VStudio/MSDN, VStudio should kill the process when VStudio/MSDN terminates. Why did this not happen? Also, 50% of a dual-Xeon system is a whole lot of CPU resources to consume. How can dexplore.exe be configured to use a more reasonable amount of CPU?
Thanks for the help.
I have similar issues. I'm not sure that the process using up 100% CPU (or 50% in the case of dual CPU etc.) is of itself an issue - so long as the thread doesn't hog the CPU at the expense of other processes. I've seen similar before with MS Access where it takes up all the available CPU but Access makes way when other applications need to get a look in. I'm not sure if dexplore is similarly well behaved but it has the feel of not being - IE I generally notice that when my PC slows down that dexplore is running and using 50% CPU on a dual core machine....could be coincidental but I'm betting against that.
It seems to be odd that dexplore should still be running after VS is shut down. It is also odd that it finds something to do constantly. This kind of behaviour is unsettling - I'd like to know what it is doing!
I have killed dexplore in Task Manager only to find that explorer.exe then starts using 50% of CPU AND becomes unresponsive, requiring that you kill and restart Explorer.exe (or at this stage a reboot is probably safest).
Come on MS - Please explain what dexplore actually does and why it continues to do it indefinitely.
I have been using vs2005 and sp1 for months now without these issues. I have absolutely no addins. just MSDN-provided help.
I have an xp pro laptop with a core 2 duo and 1gb ram. My system started to really crawl about 30 minutes ago.I was just starting a windows form in vb.net and had a few textboxes and 20 lines of code written. I went to dynamic help while having "File" highlighted.
Task Manager said that devenv.exe (visual studio) was using 800MB !!!!!!! It took me TEN MINUTES just to save the project (yes, just to click the save button) and another 7 minutes for devenv.exe to disappear from task manager.
I will reproduce this problem with User Experience thing enabled so hopefully it will get to MS.
This is absolutely unacceptable. I have the latest version of officescan (updated) and no spyware etc...
The new "Windows Desktop Search" Indexer from MS was on 'snooze mode' the whole time as it renders Outlook 2007 unusable. Before we get into "oh, is this or that on your system, did you have too many programs running, etc.."
I got it down to just VS2005 open (all other progs closed) and it was still using 800MB of my 1000MB of RAM.
Considering I am on wireless, using Cisco VPN client you can see that under those circumstanses, I am living in the page file,
not physical RAM which explaiuns the slowdown. You cannot possibly try to attribute this to anything else when VS2005 is eating up more ram than what was probably available to the system before it bloated.
Since this is an old issue I will double-post.
Me Too.
I presume that Microsoft monitor these threads.
Judging from the dates on these posts, this issue seems to have been around for about a year.
Are Microsoft actually doing anything about this?
