Bug 5476 - Mondevelop crashes when creating a new activity with a .axml file (Designer) open
Summary: Mondevelop crashes when creating a new activity with a .axml file (Designer) ...
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Android Designer ()
Version: 3.0.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Lluis Sanchez
URL:
Depends on:
Blocks:
 
Reported: 2012-06-02 14:53 UTC by bvsimmons1204
Modified: 2012-06-07 07:16 UTC (History)
0 users

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
Screen grab of my MonoDevelop session at the time of the crash (301.83 KB, image/png)
2012-06-02 14:53 UTC, bvsimmons1204
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description bvsimmons1204 2012-06-02 14:53:29 UTC
Created attachment 2010 [details]
Screen grab of my MonoDevelop session at the time of the crash

Description of Problem:


Steps to reproduce the problem:
1. Create a new activity with an open .axml file
2. Crash dialog displayed
3. Dismiss the crash Dialog and continue


Actual Results:
crash see attached screen grab

Expected Results:
no crash

How often does this happen? 
Often, I have not nailed the sequence down 100 % but I believe the above is close

Additional Information:

Crash Dump Below:
ystem.NullReferenceException: Object reference not set to an instance of an object
  at Xamarin.AndroidDesigner.Selectors.QualifierComboSelector.Load () [0x00000] in /Users/builder/data/lanes/monodevelop-mac-3.0.2/046db1bb/source/md-addins/MonoDevelop.MonoDroid/Xamarin.AndroidDesigner/Xamarin.AndroidDesigner.Selectors/QualifierComboSelector.cs:153 
  at Xamarin.AndroidDesigner.Selectors.QualifierComboSelector.Initialize (Xamarin.AndroidDesigner.DesignerSession s) [0x00007] in /Users/builder/data/lanes/monodevelop-mac-3.0.2/046db1bb/source/md-addins/MonoDevelop.MonoDroid/Xamarin.AndroidDesigner/Xamarin.AndroidDesigner.Selectors/QualifierComboSelector.cs:142 
  at Xamarin.AndroidDesigner.DesignerWidget.HandleSessionAndroidTargetChanged (System.Object sender, System.EventArgs e) [0x00019] in /Users/builder/data/lanes/monodevelop-mac-3.0.2/046db1bb/source/md-addins/MonoDevelop.MonoDroid/Xamarin.AndroidDesigner/Xamarin.AndroidDesigner/DesignerWidget.cs:588 
  at Xamarin.AndroidDesigner.DesignerSession.set_AndroidTarget (Xamarin.AndroidDesigner.AndroidTarget value) [0x00043] in /Users/builder/data/lanes/monodevelop-mac-3.0.2/046db1bb/source/md-addins/MonoDevelop.MonoDroid/Xamarin.AndroidDesigner/Xamarin.AndroidDesigner/DesignerSession.cs:575 
  at MonoDevelop.MonoDroid.Gui.AndroidDesignerView.HandleProjectSaved (System.Object sender, MonoDevelop.Projects.SolutionItemEventArgs e) [0x0002c] in /Users/builder/data/lanes/monodevelop-mac-3.0.2/046db1bb/source/md-addins/MonoDevelop.MonoDroid/MonoDevelop.MonoDroid/Gui/AndroidDesignerView.cs:137 
  at (wrapper delegate-invoke) <Module>:invoke_void__this___object_SolutionItemEventArgs (object,MonoDevelop.Projects.SolutionItemEventArgs)
  at MonoDevelop.Projects.SolutionEntityItem.OnSaved (MonoDevelop.Projects.SolutionItemEventArgs args) [0x0000b] in /Users/builder/data/lanes/monodevelop-mac-3.0.2/046db1bb/source/monodevelop/main/src/core/MonoDevelop.Core/MonoDevelop.Projects/SolutionEntityItem.cs:357 
  at MonoDevelop.Projects.SolutionEntityItem.Save (IProgressMonitor monitor) [0x0003d] in /Users/builder/data/lanes/monodevelop-mac-3.0.2/046db1bb/source/monodevelop/main/src/core/MonoDevelop.Core/MonoDevelop.Projects/SolutionEntityItem.cs:254 
  at MonoDevelop.MonoDroid.MonoDroidProject.Save (IProgressMonitor monitor) [0x00000] in /Users/builder/data/lanes/monodevelop-mac-3.0.2/046db1bb/source/md-addins/MonoDevelop.MonoDroid/MonoDevelop.MonoDroid/MonoDroidProject.cs:257 
  at MonoDevelop.Ide.ProjectOperations.Save (MonoDevelop.Projects.SolutionEntityItem entry) [0x0004b] in /Users/builder/data/lanes/monodevelop-mac-3.0.2/046db1bb/source/monodevelop/main/src/core/MonoDevelop.Ide/MonoDevelop.Ide/ProjectOperations.cs:352
Comment 1 Lluis Sanchez 2012-06-07 07:16:12 UTC
This will be fixed in MonoDevelop 3.0.3