Bug 13418 - XML editor causes XS crash after confirming auto completion of close tag
Summary: XML editor causes XS crash after confirming auto completion of close tag
Status: RESOLVED DUPLICATE of bug 13284
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: XML Editor ()
Version: unspecified
Hardware: PC Linux
: --- normal
Target Milestone: master
Assignee: Mikayla Hutchinson [MSFT]
URL:
Depends on:
Blocks:
 
Reported: 2013-07-23 14:10 UTC by Atsushi Eno
Modified: 2013-07-23 17:05 UTC (History)
1 user (show)

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

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 DUPLICATE of bug 13284

Description Atsushi Eno 2013-07-23 14:10:44 UTC
Repro steps:
- Create any project.
- Create an empty file, with ".xml" extension.
- Open the xml file, and type "<root>". After typing '>' it will show auto completion candidate "</root>"
- Type enter.

->

System.NullReferenceException: Object reference not set to an instance of an object

Server stack trace: 
  at MonoDevelop.Ide.MessageService+InternalMessageService.ShowException (Gtk.Window parent, System.String title, System.String message, System.Exception e, MonoDevelop.Ide.AlertButton[] buttons) [0x00000] in <filename unknown>:0 
  at (wrapper managed-to-native) System.Runtime.Remoting.RemotingServices:InternalExecute (System.Reflection.MethodBase,object,object[],object[]&)
  at System.Runtime.Remoting.RemotingServices.InternalExecuteMessage (System.MarshalByRefObject target, IMethodCallMessage reqMsg) [0x000c2] in /svn/mono/mcs/class/corlib/System.Runtime.Remoting/RemotingServices.cs:151 

Exception rethrown at [0]: 

  at MonoDevelop.Ide.MessageService+InternalMessageService.ShowException (Gtk.Window parent, System.String title, System.String message, System.Exception e, MonoDevelop.Ide.AlertButton[] buttons) [0x00000] in <filename unknown>:0 
  at (wrapper managed-to-native) System.Runtime.Remoting.RemotingServices:InternalExecute (System.Reflection.MethodBase,object,object[],object[]&)
  at System.Runtime.Remoting.RemotingServices.InternalExecuteMessage (System.MarshalByRefObject target, IMethodCallMessage reqMsg) [0x000c2] in /svn/mono/mcs/class/corlib/System.Runtime.Remoting/RemotingServices.cs:151 

--------
monodevelop [master/b721655] with mono [master/d62166b]. I might have some obstacle addins locally though.
Comment 1 Mikayla Hutchinson [MSFT] 2013-07-23 17:05:15 UTC

*** This bug has been marked as a duplicate of bug 13284 ***