Bug 26343 - Vs crashes with ios designer (storyboard)
Summary: Vs crashes with ios designer (storyboard)
Status: RESOLVED NOT_REPRODUCIBLE
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS Designer ()
Version: 3.9
Hardware: PC Windows
: High major
Target Milestone: ---
Assignee: Vinicius Jarina
URL:
Depends on:
Blocks:
 
Reported: 2015-01-23 09:34 UTC by Marco
Modified: 2015-03-04 07:25 UTC (History)
7 users (show)

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


Attachments
Log with the ios designer crash (1.38 KB, application/octet-stream)
2015-01-26 03:50 UTC, Marco
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 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 Marco 2015-01-23 09:34:22 UTC
Almost every time I use the ios designer under VS, VS crashes!
The log is:

Unhandled Exception
System.ArgumentNullException: Value cannot be null.
Parameter name: container
   at System.Windows.Controls.ItemContainerGenerator.ItemFromContainer(DependencyObject container)
   at System.Windows.Controls.VirtualizingStackPanel.CleanupContainers(Int32 firstItemInExtendedViewportIndex, Int32 itemsInExtendedViewportCount, ItemsControl itemsControl, Boolean timeBound, Int32 startTickCount)
   at System.Windows.Controls.VirtualizingStackPanel.CleanUp()
   at System.Windows.Controls.VirtualizingStackPanel.OnCleanUp(Object args)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)



My versions:
Xamarin 3.9.274.0
Xamarin.iOS 8.6.1.0
Visual studio PRO 2013 Update 4

The problem is very annoying, when i make a double click on a button to create a click method, at 90% VS crashes.

Thank
Comment 1 Mohit Kheterpal 2015-01-23 10:21:34 UTC
I have tried to reproduce this issue but I am not sure about the steps, I have tired it by creating a template application and then open storyboard file and it open successfully.

Could you please share your storyboard file? So that we can reproduce this issue at our end.

And it would be helpful if you share IDE logs and VSiOS designer log.

IDE Logs on windows -> Help-> Zip Xamarin Logs
VSiOS designer log on Mac-> ~/Library/Logs/Xamarin/MonoTouchVS/iOSDesigner
Comment 2 Marco 2015-01-26 03:50:54 UTC
Created attachment 9496 [details]
Log with the ios designer crash
Comment 3 Marco 2015-01-26 03:54:23 UTC
The errors appear also with a new blank storyboard (with Universal Storyboard view controller), so I think it's independent from my storyboard.
Comment 4 Alan McGovern 2015-01-26 11:27:40 UTC
I'm not entirely sure if this is an issue with the designer as the stacktrace in the first comment does not contain designer code and the log files have exceptions coming from insights:

System.NullReferenceException: Object reference not set to an instance of an object.
   at Xamarin.InsightsCore.PlatformServices.<>c__DisplayClass4.<GetDeviceInfoData>b__3()
   at System.Threading.Tasks.Task`1.InnerInvoke()
   at System.Threading.Tasks.Task.Execute()

CCing joj and alo in case this error is something unrelated that was fixed already. Jarina will still take a quick look if there's no further update.
Comment 5 Alan McGovern 2015-03-04 07:25:02 UTC
We have not been able to reproduce the problem you've described and the log files you've provided don't have this crash in them.

We have fixed some issues with the outline panel which appear to be unrelated to this exact crash, but there's a chance those 'unrelated' fixes did also fix this. These fixes should ship with every release newer than 3.9, so if you can still reproduce the issue with 3.10+, or with WatchKit enabled builds when we ship those, please reopen the bug and attach the log files again.