Question

Using the latest version of FogBugz plug-in and I get a crash message from VS2010 when I start up.

Crash details below:

  Problem Event Name:   CLR20r3
  Problem Signature 01: devenv.exe
  Problem Signature 02: 10.0.30319.1
  Problem Signature 03: 4ba1fab3
  Problem Signature 04: FogBugzForVisualStudio
  Problem Signature 05: 3.0.3958.28123
  Problem Signature 06: 4cd07687
  Problem Signature 07: fd
  Problem Signature 08: c0
  Problem Signature 09: System.NullReferenceException
  OS Version:           6.1.7600.2.0.0.256.1
  Locale ID:            2057

Additional information about the problem:
  LCID: 1033

Interesting that I restart VS in Admin mode and it works, even when restarted without admin privilages subsequently.

Answer 1

I have been able to reproduce it. If I don't run-as admin and I try to view the window (via the view menu) it crashes. When I run as admin the window always displays. Here's the signature from the crash.

Problem signature: Problem Event Name: APPCRASH Application Name: devenv.exe Application Version: 10.0.30319.1 Application Timestamp: 4ba1fab3 Fault Module Name: StackHash_0a9e Fault Module Version: 0.0.0.0 Fault Module Timestamp: 00000000 Exception Code: c0000005 Exception Offset: 01eaefaf OS Version: 6.1.7600.2.0.0.256.1 Locale ID: 1033 Additional Information 1: 0a9e Additional Information 2: 0a9e372d3b4ad19135b953a78882e789 Additional Information 3: 0a9e

Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

By the way there is a simple workaround (in win7 anyway) to allow you to run-as admin by just clicking on the taskbar button without going through a bunch of context menus just to get to the run-as admin selection:

1. Right click the vs10 taskbar icon
2. Right click the actual program and select properties
3. From the 'Shortcut' tab select 'Advanced'
4. Check 'Run as administrator'

Now whenever you click on the taskbar icon it will always run in admin mode and that has solved (at least for me) the crash that the Fogbugz addin is causing when in non-admin mode.

Answer 2

I have a similar problem, but not exactly the same. I didn't get a crash in normal user mode, but it didn't start the FogBugz AddIn. As admin, everything seem to be perfect.

Maybe it is a Windows 7 (x64) Problem?

Answer 3

I experience the same crash upon starting Visual Studio 2010 ultimate (SP1Rel) immediately after installing your addin on a Windows 7 64 bit system. The crash report below indicates a System.UnauthorizedAccess exception, but I don't see what is being accessed.

When running Visual Studio as an administrator it does not crash. Uninstalling your add-in made the problem go away, so it's definately something that needs to be fixed on your end.

In all cases I had your add in window enabled, and it crashes using normal user priviledges consistently. (ie. Running once under administrative credentials did not fix normal mode)

EventType=CLR20r3
WOW64=1
Response.type=4
Sig[0].Name=Problem Signature 01
Sig[0].Value=devenv.exe
Sig[1].Name=Problem Signature 02
Sig[1].Value=10.0.40219.1
Sig[2].Name=Problem Signature 03
Sig[2].Value=4d5f2a73
Sig[3].Name=Problem Signature 04
Sig[3].Value=mscorlib
Sig[4].Name=Problem Signature 05
Sig[4].Value=4.0.0.0
Sig[5].Name=Problem Signature 06
Sig[5].Value=4ec9f77a
Sig[6].Name=Problem Signature 07
Sig[6].Value=3790
Sig[7].Name=Problem Signature 08
Sig[7].Value=3e
Sig[8].Name=Problem Signature 09
Sig[8].Value=System.UnauthorizedAccess
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe
UI[3]=Microsoft Visual Studio has encountered a problem and needs to close.
UI[4]=If you had files open that contained unsaved changes, these changes might be lost.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
Sec[0].Key=LCID
Sec[0].Value=1033
FriendlyEventName=Stopped working
ConsentKey=CLR20r3
AppName=Microsoft Visual Studio

Answer 4

I installed the add-in today; VS2010, Windows 7 SP1 64-bit. As with others, when I started VS2010 (non-admin), the add-in was installed and marked to start with VS, but the View->Other->FogBugz command did not cause the window to appear.

I restarted VS2010, admin this time; the window appeared and I was able to log in, but VS crashed afterward, and continued to crash whether I started VS admin or non-admin.

The error in another report hinted at an UnauthorizedAccess exception. I used Sysinternals Procmon to watch VS2010's activity. There was an attempt to open the file C:\Program Files (x86)\FogBugz\FogBugz for Visual Studio\VS9.0\FogBugzForVisualStudio.AddIn for writing (!), which failed, naturally.

Unlike others, I see no evidence of the add-in in my My Documents folder.

Hope this provides more data toward a solution. Thanks!