VS2013 crashes 30 seconds after signing-in to my account from the environment... - by Peter Eliyahu Kornfeld

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
0
Sign in
to vote
ID 800759 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 9/15/2013 1:02:29 AM
Access Restriction Public

Description

After installing RC i noticed the sign-in options and gave it a try...
But, after about 30 second from the sign-in the environment crashes, and crashes after restart too.
I was able to sign out within 20 seconds from stat and VS does not crashed.
Sign in to post a comment.
Posted by Deon [MSFT] on 6/6/2014 at 9:54 AM
Thank you for using Visual Studio and for reporting this bug. We are happy to let you know that this issue has been fixed in Visual Studio 2013 Update 2. If you already have Visual Studio 2013, you can upgrade to Update 2 for free or you can install a trial version from: http://go.microsoft.com/?linkid=9832436
Posted by Peter Eliyahu Kornfeld on 10/28/2013 at 12:35 AM
Hi,

Just installed VS2013 final (12.0.21005.1 REL - Premium) and the sign-in functionality no longer crashes the IDE!!!

I believe you can close this bug :-)
Posted by Peter Eliyahu Kornfeld on 10/5/2013 at 11:10 PM
Hi,

C:\Program Files\Common Files\microsoft shared\Team Foundation Server\12.0\Microsoft.ServiceBus.dll - 2.1.30702.1

C:\Program Files\Microsoft Visual Studio 12.0\Common7\IDE\Extensions\Microsoft\SharePoint\Dependencies\Microsoft.ServiceBus.dll - 1.8.0.0

About the live meeting. I have to know what you need from me to set up the meeting, but no objection to do it...

Regards
Peter
Posted by Manish [MSFT] on 10/2/2013 at 11:52 AM
Hi Peter,
could you please the version of "Microsoft.servicebus.dll"?

This dll should be present in two places
•    C:\Program Files\Common Files\microsoft shared\Team Foundation Server\12.0\
    You can find the file version using the following steps:
        1. Open the File Explorer
        2. In File Explorer, navigate to "C:\Program Files\Common Files\microsoft shared\Team Foundation Server\12.0\ ".
        3. Find the file "Microsoft.servicebus.dll".
        4. Right-click on "Microsoft.servicebus.dll" and click Properties.
        5. In the Properties window, click the "Details" tab.
        6. The "File version" should appear in the list.


•    C:\Program Files\Microsoft Visual Studio 12.0\Common7\IDE\Extensions\Microsoft\SharePoint\Dependencies
    You can find the file version using the following steps:
        1. Open the File Explorer
        2. In File Explorer, navigate to " C:\Program Files\Microsoft Visual Studio 12.0\Common7\IDE\Extensions\Microsoft\SharePoint\Dependencies".
        3. Find the file "Microsoft.servicebus.dll".
        4. Right-click on "Microsoft.servicebus.dll" and click Properties.
        5. In the Properties window, click the "Details" tab.
        6. The "File version" should appear in the list.

Is it possible for you to have a live meeting session with us so that we can investigate the issue quickly?
You can reply to maojha@microsoft.com

Thanks
Manish Ojha
Posted by Peter Eliyahu Kornfeld on 10/1/2013 at 10:24 PM
Hi,

The version is 12.0.20827.3
Posted by Ron [MSFT] on 10/1/2013 at 3:54 PM
Peter,

Could you provide the file version of "Microsoft.VisualStudio.Services.Client.dll"? You can find the file version using the following steps:

For a 64-bit OS:
1. Open the File Explorer
2. In File Explorer, navigate to "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\ReferenceAssemblies\v4.5".
3. Find the file "Microsoft.VisualStudio.Services.Client.dll".
4. Right-click on "Microsoft.VisualStudio.Services.Client.dll" and click Properties.
5. In the Properties window, click the "Details" tab.
6. The "File version" should appear in the list.

From a 32-bit OS:
1. Open the File Explorer
2. In File Explorer, navigate to "C:\Program Files\Microsoft Visual Studio 12.0\Common7\IDE\ReferenceAssemblies\v4.5".
3. Find the file "Microsoft.VisualStudio.Services.Client.dll".
4. Right-click on "Microsoft.VisualStudio.Services.Client.dll" and click Properties.
5. In the Properties window, click the "Details" tab.
6. The "File version" should appear in the list.

This will help us to further diagnose the issue.

Thanks,
Ron Buckton, Visual Studio Team
Posted by Sara [MSFT] on 9/29/2013 at 7:46 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Sara [MSFT] on 9/29/2013 at 7:45 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Carl [MSFT] on 9/24/2013 at 10:15 PM
Hi Peter,

Were you able to create a dump file? Here is another link on how to do so using visual studio:
http://blogs.msdn.com/b/debugger/archive/2009/12/30/what-is-a-dump-and-how-do-i-create-one.aspx

Let us know if you need more info

Thanks
Carl Brochu | Visual Studio Team
Posted by Art [MSFT] on 9/24/2013 at 10:12 PM
Hello,

We are very keenly interested in your dump here. The scenario you describe is not one we've see at Microsoft, and we really need more data to be able to debug the issue. it's very important that we get the dump in order to diagnose and fix the issue in the product, and time is important right now.

Thank you in advance for your quick response.
Art Leonard
Development Lead, Visual Studio IDE team
Posted by Sara [MSFT] on 9/23/2013 at 7:43 PM
Hello again. We wanted to give you a quick reminder that to efficiently investigate and reproduce your issue, we need you submit the additional information we requested. We look forward to hearing from you with this information.
Posted by Sara [MSFT] on 9/19/2013 at 8:09 PM
Hello,

More information on how to use the tool to provide feedback is published here:https://connect.microsoft.com/VisualStudio/content/content.aspx?ContentID=26698. Maybe you couldn't use the feedback tool to catch the dump(as VS couldn't start).

Can you please install a debugger on your machine (e.g., WinDbg, since Visual Studio does not start), and obtain a minidump file at the point of the crash?

You can get the minidump file with the following steps:
1.Download and install WinDbg from the link below:
http://msdn.microsoft.com/en-us/windows/hardware/gg463009.aspx
2.In WinDBG Hit F6 and choose "devenv" to attach to the VS process. (If VS is running as admin, you should be too.).
3.Create a dump file if by typing ".dump devenv.dmp".    

We look forward to hearing from you with this information.
Posted by Peter Eliyahu Kornfeld on 9/16/2013 at 11:47 PM
Hi,

From your post it is unclear how to get the dump file you ant from me.
I'v installed the Feedback Tool and reproduced the crash, but got no indication on the whereabouts of the dump file if any...
Please be more specific on how to get the dump file you need.

Regards
Peter
Posted by Sara [MSFT] on 9/16/2013 at 4:39 AM
Thanks for your feedback. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please give us a dump file so that we can conduct further research?

Visual Studio now has an extension called Microsoft Visual Studio 2013 Feedback Tool, available on the VS gallery(<http://visualstudiogallery.msdn.microsoft.com/563d1003-f0ed-498f-8ef9-f8ee1aac39fe>)

The extension allows you to
1. upload files
2. collect trace and dump files
3. collect steps while you're repro'ing the issue
4. SQM logs about VS extensions installed
5. System details (in DxDiag output)

Please submit this information to us within 4 business days. We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team
Posted by Macy [MSFT] on 9/15/2013 at 7:52 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)