Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Multiple vsjitdebugger in task manager


  • Please log in to reply
1 reply to this topic

#1 jrossh21

jrossh21

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:10:32 PM

Posted 05 November 2009 - 02:43 PM

I have a development web server on a VMWare server that I develop and test my web apps on. Recently, I've noticed that while in visual studio, it will get pretty bogged down after a while. So I opened up task manager and noticed about 200 instances of vsjitdebugger - all with about 60-65k of memory usage. So, I thought I'd better close visual studio to end those processes. But even after I closed VS, all those vsjitdebugger processes were still there. So, I restarted the server - and they went away ... for a while. No program is running, freshly restarted and they are coming back, 1 by 1. Granted it's taking a while, but by weeks end, I'll probably have upwards of 200 again.

Anybody got any insight on what may be causing this? Or how I can find out what is causing this?

BC AdBot (Login to Remove)

 


#2 Monty007

Monty007

  • Members
  • 1,151 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Australia
  • Local time:01:02 PM

Posted 06 November 2009 - 04:56 PM

Hi, Im afraid I dont know alot about Visual Studio but this link has a lot of info on the subject http://msdn.microsoft.com/en-us/library/d0b8xh0y.aspx The process you are refering to is a debugger used in Visual Studio.
To trouble shoot why this is happening download the readme file and make sue your system meets the ninimum requirements http://msdn.microsoft.com/en-us/library/4c26cc39.aspx
Also in event viewer is there and events relating to this issue?
How to use event viewer http://www.bleepingcomputer.com/forums/t/40108/how-to-use-event-viewer/
Post any results.
MCP
MSDST




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users