Bug 4536 - Frequent null reference exception on windows when building Android project
Summary: Frequent null reference exception on windows when building Android project
Status: RESOLVED DUPLICATE of bug 3083
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Android Add-in ()
Version: Trunk
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Alan McGovern
URL:
Depends on:
Blocks:
 
Reported: 2012-04-19 16:05 UTC by Alan McGovern
Modified: 2012-04-24 12:59 UTC (History)
2 users (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 3083

Description Alan McGovern 2012-04-19 16:05:38 UTC
I frequently get this if I open an Android project and immediately hit F5 to build it, but only when running on windows.

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

Server stack trace: 
   at MonoDevelop.Ide.Gui.Pad..ctor(DefaultWorkbench workbench, PadCodon content)
   at MonoDevelop.Ide.Gui.Workbench.WrapPad(PadCodon padContent)
   at MonoDevelop.Ide.Gui.Workbench.get_Pads()
   at MonoDevelop.Ide.Gui.Workbench.GetPad[T]()
   at MonoDevelop.Ide.Gui.ProgressMonitorManager.GetBuildProgressMonitor(String statusText)
   at MonoDevelop.Ide.Gui.ProgressMonitorManager.GetBuildProgressMonitor()
   at System.Runtime.Remoting.Messaging.Message.Dispatch(Object target, Boolean fExecuteInContext)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [0]: 
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at MonoDevelop.Ide.Gui.ProgressMonitorManager.GetBuildProgressMonitor()
   at MonoDevelop.Ide.ProjectOperations.Build(IBuildTarget entry)
   at MonoDevelop.Debugger.DebugHandler.Run()
   at MonoDevelop.Components.Commands.CommandHandler.Run(Object dataItem)
   at MonoDevelop.Components.Commands.CommandHandler.InternalRun(Object dataItem)
   at MonoDevelop.Components.Commands.CommandManager.DefaultDispatchCommand(ActionCommand cmd, CommandInfo info, Object dataItem, Object target, CommandSource source)
   at MonoDevelop.Components.Commands.CommandManager.DispatchCommand(Object commandId, Object dataItem, Object initialTarget, CommandSource source)
Comment 1 Lluis Sanchez 2012-04-24 12:59:51 UTC

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