Home Dashboard Directory Help
Search

VS2008 SP1 crashes when using 'Enable .NET Framework source stepping' and certain library references by Dave Black


Status: 

Closed
 as Fixed Help for as Fixed


11
0
Sign in
to vote
Type: Bug
ID: 367121
Opened: 9/10/2008 7:57:28 PM
Access Restriction: Public
2
Workaround(s)
view
10
User(s) can reproduce this bug

Description

VS2008 SP1 crashes when using the new Debugging Feature 'Enable .NET Framework source stepping' and certain library references. I have narrowed this down to one assembly in particular - Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll (version 8.0 or 9.0).

I do not know if there are more assemblies that will cause the same behavior but I know this one assembly does.

The crash info is:
Event Type:    Error
Event Source:    .NET Runtime
Event Category:    None
Event ID:    1023
Date:        9/9/2008
Time:        4:49:20 PM
User:        N/A
Computer:    VIRTUAL-DEV
Description:
.NET Runtime version 2.0.50727.3053 - Fatal Execution Engine Error (7A2E0F92) (0)

I also have the StackFrame and Registers info if that will help.
Details
Sign in to post a comment.
Posted by Harout Saryan on 12/23/2009 at 2:29 PM
Mine is even worse. everything was working fine until today. It must of been Windows updates that screwed something up. Anyway. when I open my project, and if I drag a datagridview to a form, then right click on a DGV choose Add Column it freezes. I see the memory goes up in Task manager (memory leak) then after 20-30 min it crashes with this exact error message: "An exception occurred while trying to update the data smart tasks, they will be disabled, Insufficient memory to continue the execution of the program." But this only happens with my project for some reason. it does not happen when I start a new project. I have check all my datasets and they all look fine. Also note that when I am adding the new DGV it does not have anything binded. So it's just a blank DGV all I am trying to add is add a unbounded column.

Note: I have Removed all my Dot Nets / VB / Sql and re-installed everything and still the same thing!
it's the same thing on a different machine as well.

Thx
H
12-23-09
VB 2008
SP1
Posted by DanColes on 12/2/2008 at 7:15 AM
Unfortunately I get the same problem too. Neither workaround was relevant. I can generate and upload a crash dump if it's useful. Sometimes rebooting the machine helps. The behaviour is pretty predictable:
1) Right-clicking on Toolbox and selecting "Choose Toolbox Items" - seems to always occur.
2) Right-clicking on a C# WPF project and selecting "Properties" - sometimes happens, and reboot normally fixes it for a while.
3) Right-clicking within a C# WPF project and selecting "Add - Existing Item" - regularly happens, and reboot normally fixes it for a while.

Other work-arounds I found on the internet included removing .Net 2.0 SP1 (but I have SP2 installed and not SP1), and clearing out all temporary files from several locations (but that had no effect).

I'm working on Windows XP (5.1) Build 2600.XPSP_SP3_GDR.080814-1236 : Service Pack 3. I have .Net 3.5 SP1 installed and VS2008 SP1.
Posted by fedeballan on 10/30/2008 at 4:59 AM
again with following event:
Tipo evento:    Errore
Origine evento:    Microsoft Visual Studio
Categoria evento:    Nessuno
ID evento:    1000
Data:        30/10/2008
Ora:        12.57.18
Utente:        N/D
Computer:    FEDERICO2007
Descrizione:
Faulting application devenv.exe, version 9.0.30729.1, stamp 488f2b50, faulting module ntdll.dll, version 5.1.2600.2180, stamp 41252c01, debug? 0, fault address 0x00001010.

Per ulteriori informazioni, consultare la Guida in linea e supporto tecnico all'indirizzo http://go.microsoft.com/fwlink/events.asp.
Dati:
0000: 41 00 70 00 70 00 6c 00 A.p.p.l.
0008: 69 00 63 00 61 00 74 00 i.c.a.t.
0010: 69 00 6f 00 6e 00 20 00 i.o.n. .
0018: 46 00 61 00 69 00 6c 00 F.a.i.l.
0020: 75 00 72 00 65 00 20 00 u.r.e. .
0028: 20 00 64 00 65 00 76 00    .d.e.v.
0030: 65 00 6e 00 76 00 2e 00 e.n.v...
0038: 65 00 78 00 65 00 20 00 e.x.e. .
0040: 39 00 2e 00 30 00 2e 00 9...0...
0048: 33 00 30 00 37 00 32 00 3.0.7.2.
0050: 39 00 2e 00 31 00 20 00 9...1. .
0058: 34 00 38 00 38 00 66 00 4.8.8.f.
0060: 32 00 62 00 35 00 30 00 2.b.5.0.
0068: 20 00 69 00 6e 00 20 00    .i.n. .
0070: 6e 00 74 00 64 00 6c 00 n.t.d.l.
0078: 6c 00 2e 00 64 00 6c 00 l...d.l.
0080: 6c 00 20 00 35 00 2e 00 l. .5...
0088: 31 00 2e 00 32 00 36 00 1...2.6.
0090: 30 00 30 00 2e 00 32 00 0.0...2.
0098: 31 00 38 00 30 00 20 00 1.8.0. .
00a0: 34 00 31 00 32 00 35 00 4.1.2.5.
00a8: 32 00 63 00 30 00 31 00 2.c.0.1.
00b0: 20 00 66 00 44 00 65 00    .f.D.e.
00b8: 62 00 75 00 67 00 20 00 b.u.g. .
00c0: 30 00 20 00 61 00 74 00 0. .a.t.
00c8: 20 00 6f 00 66 00 66 00    .o.f.f.
00d0: 73 00 65 00 74 00 20 00 s.e.t. .
00d8: 30 00 30 00 30 00 30 00 0.0.0.0.
00e0: 31 00 30 00 31 00 30 00 1.0.1.0.
00e8: 0d 00 0a 00             ....    
Posted by fedeballan on 10/30/2008 at 4:53 AM
- I have 'Enable .NET Framework source stepping' unchecked and the error happen too....
- see my Validation comment: it happen also while checking-in on srcSafe.
Posted by Microsoft on 10/29/2008 at 1:14 PM
Hello,

This bug fix will be available in the next release of Visual Studio (VS 2010).

Regards,
Visual Studio Debugging Team
Posted by Tabas on 10/24/2008 at 4:23 PM
Where i can get the Fix for this usse... the BUG is marked like FIXED?

Please....

Posted by Dave Black on 10/1/2008 at 12:53 PM
davekatzma,

Check out my workaround in the meantime. HTH

DaveBlack
Posted by Dave Black on 10/1/2008 at 12:51 PM
Since the status of this item has been changed to "Fixed", when and how will the fix become available? As a Hotfix? Included in a Service Pack? And when?
Posted by davekatzma on 9/29/2008 at 7:07 PM
I am having the same problem. Can anyone verify that this has been solved and if so, how?
Posted by Microsoft on 9/16/2008 at 12:24 AM
Thanks for your feedback.

We are escalating this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Thank you,
Visual Studio Product Team
Posted by Dave Black on 9/15/2008 at 9:45 PM
Please note that I noticed a typo in my "How to Reproduce" steps. I have fixed it.

Please retry both of the methods I describe to reproduce the issue.
Posted by Dave Black on 9/15/2008 at 7:07 PM
The crash dump has been posted to the URL as you requested.

BTW, I have VS 2005 Professional SP1 installed as well.
Posted by Microsoft on 9/14/2008 at 7:03 PM
Thanks for reporting the issue.
In order to fix the issue, we must first reproduce the issue in our labs. We are unable to reproduce the issue with the steps you provided.

It may help if you provide us with a dump file

You can get the dump file with the following steps:
1. Download the Debugging Tools from Windows from http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx and install. Assume that you copy it to “C:\Debuggers”.

2. Open a command line prompt. Close all unnecessary applications.

3. Try to reproduce the problem.

4. Before VS IDE crashes , execute the following command at the command line prompt:

cscript C:\Debuggers\adplus.vbs -crash -FullOnFirst -pn devenv.exe –o C:\Dump

Dump file will be generated at “C:\Dump” and it usually takes several hundred MB. Make sure that you have sufficient disk space.

5. After VS IDE crash, please go to the folder “C:\Dump”. There can be multiple .DMP files. If their size are huge, please add the first .DMP file sorted by the timestamp (e.g. the first .DMP file captured) to a zip and upload it to the workspace:
https://sftus.one.microsoft.com/choosetransfer.aspx?key=92fe38ec-a864-4156-9055-01d52f6e6b61
Password:
37DDSfqOF85a+Lg$

If we do not receive a response from you after 7-days , we will automatically close your issue. There is no obligation to respond -- at any time you may edit your issue via Connect and change the status to “Active.”

Thank you,
Visual Studio Product Team
Sign in to post a workaround.
Posted by fedeballan on 10/30/2008 at 4:52 AM
I have 'Enable .NET Framework source stepping' unchecked and the error happen too....
Posted by Dave Black on 9/10/2008 at 8:03 PM
There are 2 workarounds I've found:

1. Leave the Debugging Feature 'Enable .NET Framework source stepping' under Tools | Options | Debugging | General UNCHECKED

2. Avoid using any UnitTest projects with this Debugging Feature