Home Dashboard Directory Help
Search

Visual studio crash opening forms in design mode by Alessandro d Este


Status: 

Closed
 as Not Reproducible Help for as Not Reproducible


2
0
Sign in
to vote
Type: Bug
ID: 638822
Opened: 1/27/2011 8:22:52 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

Visual studio 2010 professional va in crash se apro in modalità design un winform da un progetto generato con Visual studio 2010 c# express (lo fa sempre, non ho trovato eccezioni).

Per andare avanti ho scoperto che se apro PRIMA il file *.Designer.cs e *.resx, poi apro il file in modalità design funziona e non mi da più il problema fino al successivo riavvio del programma.
Details
Sign in to post a comment.
Posted by Alessandro d Este on 3/4/2011 at 12:17 AM
The error for me is very easy to replicate:
- create new windows form project (or open one that already exists)
- save and close
- reopen the project and open directly the form in design mode
- CRASH!

I don't know how to help you... but I have no exception, always do it.
Thanks
Posted by Microsoft on 3/3/2011 at 7:17 PM
Thank you for your feedback.
Unfortunately, we were unable to reproduce the bug with the scenario and steps provided.

If this issue still reproduces at your end, we would like to investigate it again. Please provide the exact steps/actions to reproduce the problem or preferably a project that reproduces the issue and we will re-investigate.

Thanks,
The Windows Forms Product Team
Posted by Alessandro d Este on 2/18/2011 at 11:25 AM
the file FeedbackID-638822_Alessandro_dEste_dump.zip is uploaded.
One note:
I run the 'capture exception', the program start, i open a form for crash the VS but don't open the window with error, stay blocked waiting (I've wait for an hour...). So I've give the break command and VS closed.

I can't answer until next Thursday.

Thank you.
Posted by Microsoft on 2/15/2011 at 8:43 PM
please download the VS performance tool from: http://visualstudiogallery.msdn.microsoft.com/en-us/e8649e35-26b1-4e73-b427-c2886a0705f4 Please read the “Performance Diagnostics Tool – User Guide” document (a shortcut to it should appear on your desktop after install) on steps to generate a trace. Please note that when you uninstall the tool, the settings.ini file will not be removed as it contains your user settings. Once you collected traces, Please upload your file to workspace. Please include part of your name and issue in the perf file names, this really helps us identify between uploaded traces.
Posted by Alessandro d Este on 2/14/2011 at 7:34 AM
Hi, thank you for the immediate support. Only now I can follow this step.

I've installed the sdk, copied the file adplus.vbs in C:\Debuggers, created a directory for the log (C:\Temp\Log) and run your command:
cscript C:\Debuggers\adplus.vbs -crash -FullOnFirst -pn devenv.exe –o C:\Temp\Log

it give me this error:
[START]
C:\Users\Ade>cscript C:\Debuggers\adplus.vbs -crash -FullOnFirst -pn devenv.exe
-o "C:\Temp\Log"
Microsoft (R) Windows Script Host Versione 5.8
Copyright (C) Microsoft Corporation 1996-2001. Tutti i diritti riservati.

*** ERROR ***
Errors found reading external arguments:

Invalid command line parameter: [-o]
Invalid command line parameter: [C:\Temp\Log]
Please see ADPlus.doc for usage information
Log data below:
ADPlus Version: 6.03.006
ADPlus Version Date: 12/16/2008
OS Version: 6.1
OS Build: 7600
DateTimeStamp: Date_02-14-2011__Time_16-26-1515
ADPlus was run on: ADE
Debuggers Installation Directory: C:\Debuggers

Command line arguments used were:
-crash -FullOnFirst -pn devenv.exe -o C:\Temp\Log

[END]
I've tried to look the helps for the command and change the arguments or the order but I haven't resolved.

I'm under Windows 7, 64bit, visual studio 2010 prof.

Thank you for the support.
Posted by Microsoft on 2/3/2011 at 7:36 PM
Hi, given that we have not heard back from you in 7 days. We will go ahead and close this Connect Issue. If you get a chance to review and provide the information requested earlier, you can go ahead and reactivate this issue.
Posted by Microsoft on 1/30/2011 at 10:02 PM
I am currently standing by for an update from you and would like to know how things are going on your end. If you could get back to me at your earliest convenience with information I request, we will be able to make headway towards a resolution. I look forward to hearing from you.
Posted by Microsoft on 1/27/2011 at 7:10 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:

****************************************************************
Note: Please zip the file and use "FeedbackID-638822" as prefix of the file name

****************************************************************

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=1d9ea00a-8c28-4453-819d-30256b0b9625
Password is 9f]XUpR2Vq

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,
Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 1/27/2011 at 8:58 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)
Sign in to post a workaround.