Bug 60759 - App crashes when looking at Locals
Summary: App crashes when looking at Locals
Alias: None
Product: iOS
Classification: Xamarin
Component: Debugger ()
Version: XI 11.3 (xcode9.1)
Hardware: PC Windows
: --- normal
Target Milestone: Future Cycle (TBD)
Assignee: Bugzilla
Depends on:
Reported: 2017-11-19 11:10 UTC by kontakt
Modified: 2018-02-19 12:01 UTC (History)
4 users (show)

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:

Description kontakt 2017-11-19 11:10:03 UTC
I set a breakpoint, the app breaks and then I go to "Locals" window to inspect values of UIKit objects. When I inspect some specific UIKit objects, the app always crashes instead of showing me the values.


I inspect an UIView object and click on >base (UIResponder)
The app crashes with an error:
-[UIView pasteConfiguration]: unrecognized selector sent to instance 0x7ffe84112fe0
The app has been terminated.

I inspect UIButton:
-[UIButton adjustsImageSizeForAccessibilityContentSizeCategory]: unrecognized selector sent to instance 0x7ff7b6115620
The app has been terminated.

I inspect UIImageView:
-[UIImageView adjustsImageSizeForAccessibilityContentSizeCategory]: unrecognized selector sent to instance 0x7feac440ab70
The app has been terminated.

Sometimes it also makes VS busy and force-restart is needed.

Note that this is happening to me for a very long time now, maybe even a few years, it has never been resolved. And it is not happening only with those specific UIKit objects, it is actually happening like 30% of times when I do some values inspection. Any chance to fix this?
Currently I have Xamarin.iOS 11.3, Visual Studio 15.4.4, XCode 9.0.
Comment 1 Alex Soto [MSFT] 2017-11-20 14:51:54 UTC
Hello kontakt!

Thanks for reaching could you please supply your full version information?

The easiest way to get exact version information:
- On Visual Studio for Mac: "Visual Studio" menu, "About Visual Studio" item, "Show Details" button.

- On Visual Studio for Windows: "Help menu", "About Microsoft Visual Studio" item.
Then copy/paste the version information (you can use the "Copy Information" button).
Comment 2 kontakt 2017-11-20 15:23:25 UTC
Microsoft Visual Studio Community 2017 
Version 15.4.4
Microsoft .NET Framework
Version 4.7.02046

Installed Version: Community

Visual Basic 2017   00369-60000-00001-AA614
Microsoft Visual Basic 2017

Visual C# 2017   00369-60000-00001-AA614
Microsoft Visual C# 2017

ASP.NET and Web Tools 2017   15.0.30925.0
ASP.NET and Web Tools 2017

ASP.NET Core Razor Language Services   1.0
Provides languages services for ASP.NET Core Razor.

Azure App Service Tools v3.0.0   15.0.30915.0
Azure App Service Tools v3.0.0

Common Azure Tools   1.10
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.

JavaScript Language Service   2.0
JavaScript Language Service

JavaScript Project System   2.0
JavaScript Project System

Merq   1.1.17-rc (cba4571)
Command Bus, Event Stream and Async Manager for Visual Studio extensions.

Mono Debugging for Visual Studio   4.7.4-pre (c2d89eb)
Support for debugging Mono processes with Visual Studio.

Node.js Tools   1.4.10918.1
Adds support for developing and debugging Node.js apps in Visual Studio

NuGet Package Manager   4.4.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.

TypeScript tools for Visual Studio

Visual Studio Code Debug Adapter Host Package   1.0
Interop layer for hosting Visual Studio Code debug adapters in Visual Studio

VisualStudio.IoT   1.0
Package with IoT components for Visual Studio

VisualStudio.Mac   1.0
Mac Extension for Visual Studio

Xamarin (34c1b6c)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.

Xamarin.Android SDK (HEAD/c2a33d8ea)
Xamarin.Android Reference Assemblies and MSBuild support.

Xamarin.iOS and Xamarin.Mac SDK (51128b8)
Xamarin.iOS and Xamarin.Mac Reference Assemblies and MSBuild support.
Comment 3 kontakt 2017-12-05 23:32:34 UTC
Status of this bug is still NEEDINFO, do you need anything else?
Comment 4 Manuel de la Peña [MSFT] 2018-01-10 09:57:52 UTC
Hello, could you please provide a small sample that we could use to reproduce the bug. That way I'll be able to reproduce the bug and try to triage it or even provide a solution
Comment 5 Vincent Dondain [MSFT] 2018-02-16 21:32:13 UTC
We have not received the requested information. If you are still experiencing this issue please provide all the requested information and re-open the bug report. Thanks!
Comment 6 kontakt 2018-02-17 00:27:31 UTC
It is still happening, sorry, I am too busy to put together some sample code, but it seems pretty straightforward from the description I provided and doesn't seem to be happening based on something project-specific. Did you at least try it? Don't get me wrong, but I was hoping that it is the Xamarin team who does what it takes to fight the bugs, not the Xamarin user.
Comment 7 Manuel de la Peña [MSFT] 2018-02-19 12:01:53 UTC
@kontakt unfortunately, although we do our best to reproduce the issue, we are not able to re-create a sample project that reproduce it.

In order to be able to move fwd we need that information from the user since we might be taking some assumptions that are wrong. Code speaks better when we want to reproduce bugs and in this case, 3 different engineers have tried in a local project and have not been able to reproduce the issue in their system.

Therefore, feel free to reopen the bug if you consider that the bug was not fixed in the latests stable release, maybe, if you can just copy paste a small sample of the code that crashes we might be able to incorporate it to the common samples we use, confirm it and move to try and fix this problem.