Bug 51633 - Freeze when debugging [Android] [Xamarin.Forms]
Summary: Freeze when debugging [Android] [Xamarin.Forms]
Status: RESOLVED NORESPONSE
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Debugger ()
Version: 4.2.0 (C8)
Hardware: PC Windows
: High normal
Target Milestone: 4.4.0 (C10)
Assignee: Joaquin Jares
URL:
Depends on:
Blocks:
 
Reported: 2017-01-19 09:46 UTC by anton.duzenko@gmail.com
Modified: 2017-06-28 17:08 UTC (History)
4 users (show)

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


Attachments
Freeze Screenshot (399.45 KB, image/png)
2017-01-30 15:18 UTC, anton.duzenko@gmail.com
Details
Attach to frozen process (37.63 KB, image/png)
2017-01-30 15:25 UTC, anton.duzenko@gmail.com
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 NORESPONSE

Description anton.duzenko@gmail.com 2017-01-19 09:46:22 UTC
This is a Xamarin.Forms application.
The application is being tested on an Android 6.0 phone.
Basic operation is to perform a HTTP-request and parse the result as a JSON.
If a response is not a valid JSON an exception is thrown.
I added the Newtonsoft.Json.JsonReaderException to the list of exception for VS2015 debugger to stop at throw.
Soon after the debugger stops VS2015 freezes and the VS2015 is busy with internal something pops up.
The freeze may or may not be triggered by hovering the mouse over identifiers.
Comment 1 anton.duzenko@gmail.com 2017-01-19 09:48:16 UTC
Xamarin and VS2015 are both the latest stable versions.
Comment 2 anton.duzenko@gmail.com 2017-01-19 10:34:33 UTC
Same happens in VS2017 RC
Comment 3 anton.duzenko@gmail.com 2017-01-19 10:53:51 UTC
VS2013 crashes.
Comment 4 Emanuel 2017-01-19 12:57:17 UTC
Moving this bug to C10 for proper investigation.

@Anton, could you attach the content of the Debug output pane?

Thanks for reporting!
Comment 5 anton.duzenko@gmail.com 2017-01-19 13:13:22 UTC
You mean the screenshot of the frozen window?
Comment 6 Emanuel 2017-01-19 14:05:03 UTC
It'd be great if you can grab the text of the Debut Output window. If VS is completely hanged/frozen a screenshot of that window could be also helpful. 

To open the Debug output you can do the following:
1- Go to View -> Output, to open the Output Window.
2- Then, in the Output window select 'Debug' in the 'Show output from' dropdown. ('Debug' will only be available right after starting a debug session)
Comment 7 anton.duzenko@gmail.com 2017-01-30 15:18:58 UTC
Created attachment 19644 [details]
Freeze Screenshot
Comment 8 anton.duzenko@gmail.com 2017-01-30 15:19:47 UTC
Just happened again. What I did here was alt-tabb to firefox and back -> freeze.
Comment 9 anton.duzenko@gmail.com 2017-01-30 15:24:40 UTC
Started another instance of VS2015 and tried to attach to the frozen process.
Got that: (see another screenshot).
Then created a dump file sized about 1GB - let me know how I can send it to you.
Comment 10 anton.duzenko@gmail.com 2017-01-30 15:25:04 UTC
Created attachment 19645 [details]
Attach to frozen process
Comment 11 Joaquin Jares 2017-05-23 14:07:55 UTC
15.0 had an install issue where sometimes the debugger will not properly install. This should not happen anymore in 15.2. Also, was the app debugging at all? If it was, then this is something different. Debug output will help identify the issue (as Emanuel commented, go to Debug -> Output and copy everything in the output window).
Comment 12 Joaquin Jares 2017-06-28 17:08:33 UTC
I'm marking this as no response. Please feel free to reopen if it's still happening to you.