Visual Studio disappears during Get Latest Version

Visual Studio disappears during Get Latest Version

• Subhosh

  Unfortunately, I cannot comment directly on the ship dates for VS 2005 SP1.

  I can refer you to Brian Harry's blog (http://blogs.msdn.com/bharry) which contains the following quote:

  "Some good news is that the TFS SP1 that will be available later this year ...".

  Thanks,
  Ben

  
  
  

• Ofir Epstein

  Well that helps a lot! Just out of curiousity, where did you get symbols for all of these

  I managed to track down a duplicate issue in our work item tracking database that has the same stack trace and general symptoms (i.e. large number of files -- 5000- and VS crashes with a Stack Overflow). This bug has been fixed and the fix should be part of VS 2005 Service Pack 1. In the meantime, you can work around the issue by either using Source Control Explorer or the command line to perform a Get on a solution with more than 3000 or 4000 files. I should note that other Solution Manager context menu items (and not just SCC ones) may be subject to this bug. Unfortunatley, I don't have an exhaustive list of which commands are affected.

  If you need this fixed prior to the release of Service Pack 1 then I suggest you contact our support organization to escalate your incident. I have not been able to ascertain whether a QFE already exists.

  Thanks,

  Ben Ryan

  
  
  

• Snickel65

  Hello,

  we are formulating more specific diagnostic questions, but meanwhile could you tell us how many files the solution includes

  Thanks

  
  
  

• EtherealSky

  There are no events generated when this occurs.

  Get latest version from the Source Control Explorer works fine even when the solution is loaded. I tried both a regular get and a forced get.

  If I select the projects from the solution tree and Get Latest (Instead of selecting the solution), the problem occurs as long as most of the projects are selected, say 74 of the 76 projects. In cases of failure, Visual Studio disappears before displaying the Get Progress dialog.

  I have also tried deleting the bin and debug directories.

  We have noticed the problem on 3 other machines.

  My Team Explorer version:

  Microsoft Visual Studio 2005 Team Explorer
  Version 8.0.50727.147

  
  

• K.Kong

  Hello,

  could you check if there are any events generated when this occurs (Computer Managment->System Tools>Event Viewer) Is the same thing happens when you do Get Latest Version

  • from Source Control Explorer, while the solution is open
  • from Source Control Explorer, while the solution is closed

  Are you using RTM version of Team Explorer

  Thanks

  
  
  

• s.sanya

  Jeff,

  Could you try bring up a second instance of Visual Studio, Go to Tools->Attach to Process and attach the debugger to the devenv.exe where you will reproduce the problem. Be sure to click the "Select" button to the right of "Attach to" and click on both Managed and Native code types. After you are attached, go to Debug->Exceptions and click on all of the checkboxes under the "Thrown" column.

  Ideally this will permit us to capture the exception and call stack at the point your VS instance is dying.

  Assuming it breaks at an exception during the Get, you can bring up the Call Stack tool window (Debug->Windows), right click and choose Select All within that tool window and then right click copy to capture the stack. You should also be able to glean some information about the exception by bringing up the Locals tool window and looking for an exception object in there.

  When you are done, you will probably want to go back to Debug->Exceptions and uncheck all of those boxes under the Thrown column.

  Your problem sounds like some type of unhandled exception that is happening on a background thread or somewhere else in the Get path such that VS terminates. Unfortunately (or "fortunately" depending upon your viewpoint) we have not seen this before, so we need to narrow down where the issue occurs.

  Thanks,
  Ben Ryan

  
  
  

• JustbobChico

  Hi Ben,

  Thanks for the update.

  I got the symbols to show up by downloading the Debugging Tools for Windows and then using symchk to get the symbol files. After a few simple settings in Visual Studio, there they were!

  We can live with the workaround until the service pack is released. Do you know if it is still on schedule for Q3 as mentioned below

  http://msdn.microsoft.com/vstudio/support/servicing/sp1_vs05/default.aspx

  Jeff

  
  

• FWX

  Hi Ben,

  Following your instructions, the exception generated was a stack overflow. Here is the call stack:

  
  > ntdll.dll!7c9106a6()
  [Frames below may be incorrect and/or missing, no symbols loaded for ntdll.dll]
  ntdll.dll!7c910732()
  ntdll.dll!7c911538()
  ntdll.dll!7c911596()
  ntdll.dll!7c9106eb()
  ntdll.dll!7c911bff()
  ntdll.dll!7c91825d()
  ntdll.dll!7c911538()
  ntdll.dll!7c911596()
  ntdll.dll!7c9106eb()
  ntdll.dll!7c910732()
  msenv.dll!50401448()
  msenv.dll!50330103()
  msenv.dll!50330440()
  msenv.dll!5033041e()
  msenv.dll!5033041e()
  msenv.dll!5033041e()
  msenv.dll!5033041e()
  msenv.dll!5033041e()
  msenv.dll!5033041e()
  msenv.dll!5033041e()
  msenv.dll!5033041e()
  ...
  msenv.dll!5033041e()
  
  

  
  

• TFCNE

  We have 4235 files in our solution.

  I tried this again with symbols loaded:

  First-chance exception at 0x7c9106a6 (ntdll.dll) in devenv.exe: 0xC00000FD: Stack overflow.

  > ntdll.dll!_RtlAllocateHeap@12()  + 0xd2 bytes 
    msenv.dll!CByteHash::DoHashLookup()  + 0x129 bytes 
    msenv.dll!CByteHash::AddString()  + 0x30 bytes 
    msenv.dll!CXMLMemberIndexService::HandsOffOrOnFiles()  + 0xa8 bytes 
    msenv.dll!CXMLMemberIndexService::HandsOffFiles()  + 0x1a bytes 
    msenv.dll!NVseePkgsVsScci::CTrackProjectDocumentsService::HandsOffFiles()  - 0x80 bytes 
    Tfsprovider.dll!NVseePkgsVssProvider::CFilesInvolvedInSourceControlOperation::VRequestHandsOffInvolvedFiles()  + 0x43 bytes 
    Tfsprovider.dll!NVseePkgsVssProvider::CFilesInvolvedInSourceControlOperation::CFilesInvolvedInSourceControlOperation()  + 0x49b bytes 
    Tfsprovider.dll!NVseePkgsVssProvider::CAbstractionLayerDispatcher::vApplyChanges()  + 0x280 bytes 
    Tfsprovider.dll!NVseePkgsVssProvider::CSccGetTransaction::vApplyChanges()  + 0x968 bytes 
    Tfsprovider.dll!NVseeLibVapiTransaction::CGetTransaction<NVseePkgsVssProvider::CSccTransaction>::fDoSccCommand()  + 0x40 bytes 
    Tfsprovider.dll!NVseeLibVapiTransaction::CTransaction::fPerformSccOperation()  + 0x32 bytes 
    Tfsprovider.dll!NVseePkgsVssProvider::CSccTransaction::vInitiateSccOperation()  + 0x10f bytes 
    Tfsprovider.dll!CVsSccUI::Exec_icmdSccGetLatestVersion()  + 0x63a bytes 
    Tfsprovider.dll!CVsCommandTargetMap<NVseePkgsVssProvider::CCheckInHelper,IxNull>::Exec()  + 0xa5 bytes 
    Tfsprovider.dll!CVsCommandTarget<CVsSccPackage,IOleCommandTarget>::Exec()  + 0x24 bytes 
    Tfsprovider.dll!CVsSccPackage::Exec()  + 0x164 bytes 
    msenv.dll!CVSCommandTarget::ExecCmd()  + 0xf594 bytes 
    msenv.dll!CVSCommandTarget::Exec()  + 0x4e bytes 
    msenv.dll!FnwpPropBar()  + 0xd7e39 bytes 
    user32.dll!_InternalCallWinProc@20()  + 0x28 bytes 
    user32.dll!_UserCallWinProcCheckWow@32()  + 0xb7 bytes 
    user32.dll!_DispatchMessageWorker@8()  + 0xdc bytes 
    user32.dll!_DispatchMessageW@4()  + 0xf bytes 
    msenv.dll!EnvironmentMsgLoop()  + 0xda bytes 
    msenv.dll!CMsoCMHandler::FPushMessageLoop()  + 0x1f bytes 
    msenv.dll!SCM::FPushMessageLoop()  + 0x4d bytes 
    msenv.dll!SCM_MsoCompMgr::FPushMessageLoop()  + 0x27 bytes 
    msenv.dll!CMsoComponent::PushMsgLoop()  + 0x25 bytes 
    msenv.dll!VStudioMainLogged()  + 0x16a bytes 
    devenv.exe!0040952e()  
    [Frames below may be incorrect and/or missing, no symbols loaded for devenv.exe] 
    devenv.exe!0040685f()  
    ntdll.dll!_LdrpGetProcedureAddress@20()  + 0xe7 bytes 
    ntdll.dll!_LdrGetProcedureAddress@16()  + 0x18 bytes 
    kernel32.dll!_GetProcAddress@8()  + 0x3e bytes 
    devenv.exe!00401d34()  
    devenv.exe!00401d7d()  
    devenv.exe!00406a3c()  
    devenv.exe!00406aa9()  
    kernel32.dll!_BaseProcessStart@4()  + 0x23 bytes 
  
  

  
  
• Visual Studio disappears during Get Latest Version