Bug 352 - Crash on changing project file property
Summary: Crash on changing project file property
Status: RESOLVED NOT_REPRODUCIBLE
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Shell ()
Version: Trunk
Hardware: PC Windows
: Normal major
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2011-08-20 09:14 UTC by Mikayla Hutchinson [MSFT]
Modified: 2016-12-13 21:13 UTC (History)
4 users (show)

Tags: gtk
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 NOT_REPRODUCIBLE

Description Mikayla Hutchinson [MSFT] 2011-08-20 09:14:55 UTC
When changing the "copy to output" property of a file in the solution pad, MD hard crashed.

ERROR [2011-08-20 14:09:13Z]: Unhandled Exception
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
   at System.Threading.Thread.InternalCrossContextCallback(Context ctx, IntPtr ctxID, Int32 appDomainID, InternalCrossContextDelegate ftnToCall, Object[] args)
   at System.Runtime.Remoting.Channels.CrossContextChannel.SyncProcessMessage(IMessage reqMsg)
   at System.Runtime.Remoting.Proxies.RemotingProxy.CallProcessMessage(IMessageSink ms, IMessage reqMsg, ArrayWithSize proxySinks, Thread currentThread, Context currentContext, Boolean bSkippingContextChain)
   at System.Runtime.Remoting.Proxies.RemotingProxy.InternalInvoke(IMethodCallMessage reqMcmMsg, Boolean useDispatchMessage, Int32 callType)
   at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(IMessage reqMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at MonoDevelop.Ide.Gui.ProgressMonitorManager.GetSaveProgressMonitor(Boolean lockGui)
   at MonoDevelop.Ide.ProjectOperations.Save(SolutionEntityItem entry) in c:\Users\Michael\work\monodevelop\main\src\core\MonoDevelop.Ide\MonoDevelop.Ide\ProjectOperations.cs:line 349
   at MonoDevelop.Ide.ProjectOperations.Save(IWorkspaceFileObject item) in c:\Users\Michael\work\monodevelop\main\src\core\MonoDevelop.Ide\MonoDevelop.Ide\ProjectOperations.cs:line 439
   at MonoDevelop.DesignerSupport.Projects.ComponentNodeCommandHandler.OnChanged(Object obj) in c:\Users\Michael\work\monodevelop\main\src\addins\MonoDevelop.DesignerSupport\MonoDevelop.DesignerSupport.Projects\ComponentNodeBuilder.cs:line 47
   at MonoDevelop.DesignerSupport.DesignerSupportService.OnPropertyGridChanged(Object s, EventArgs a) in c:\Users\Michael\work\monodevelop\main\src\addins\MonoDevelop.DesignerSupport\MonoDevelop.DesignerSupport\DesignerSupportService.cs:line 179
   at System.EventHandler.Invoke(Object sender, EventArgs e)
   at MonoDevelop.Components.PropertyGrid.PropertyGridTree.<OnObjectChanged>b__0() in c:\UserSystem.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
   at System.Threading.Thread.InternalCrossContextCallback(Context ctx, IntPtr ctxID, Int32 appDomainID, InternalCrossContextDelegate ftnToCall, Object[] args)
   at System.Runtime.Remoting.Channels.CrossContextChannel.SyncProcessMessage(IMessage reqMsg)
   at System.Runtime.Remoting.Proxies.RemotingProxy.CallProcessMessage(IMessageSink ms, IMessage reqMsg, ArrayWithSize proxySinks, Thread currentThread, Context currentContext, Boolean bSkippingContextChain)
   at System.Runtime.Remoting.Proxies.RemotingProxy.InternalInvoke(IMethodCallMessage reqMcmMsg, Boolean useDispatchMessage, Int32 callType)
   at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(IMessage reqMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at MonoDevelop.Ide.MessageService.InternalMessageService.ShowException(Window parent, Exception e, String primaryText)
   at MonoDevelop.Ide.MessageService.ShowException(Window parent, Exception e, String primaryText) in c:\Users\Michael\work\monodevelop\main\src\core\MonoDevelop.Ide\MonoDevelop.Ide\MessageService.cs:line 158
   at MonoDevelop.Ide.Messags\Michael\work\monodevelop\main\src\core\MonoDevelop.Ide\MonoDevelop.Components.PropertyGrid\PropertyGridTree.cs:line 268
   at GLib.Timeout.TimeoutProxy.Handler()
Comment 1 Marius Ungureanu 2013-11-23 09:31:47 UTC
Can this bug be closed?
Comment 2 Greg Munn 2016-12-13 21:13:41 UTC
It's probably safe to say that this isn't the case anymore - can't repro.