Bug 3141 - Repeatedly switching between calls in the call stack causes app crash
Summary: Repeatedly switching between calls in the call stack causes app crash
Status: CLOSED INVALID
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: 2.8.6
Hardware: PC Mac OS
: --- minor
Target Milestone: ---
Assignee: Jeffrey Stedfast
URL:
Depends on:
Blocks:
 
Reported: 2012-01-30 11:43 UTC by PJ
Modified: 2012-01-30 14:41 UTC (History)
1 user (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:
CLOSED INVALID

Description PJ 2012-01-30 11:43:35 UTC
Testing bug 3043, I decided to double click the calls in the call stack and found that I could semi-reliably crash the application when switching between them.

Open SimpleTextView.sln (from monotouch-samples)
Open SimpleTextInputViewController.cs

Set a breakpoint on line 25 (though I tested it on a few lines)

Debug the application. As the app loads, it should hit the breakpoint right away.

In the call stack (while BP is hit), double click each of the calls repeatedly.

http://screencast.com/t/qxmd9rgMIkV

(I know this was on line 26, I was testing to see if BP location mattered -it didn't)

Seems to take a lot of switching to trigger the app crash.

Application output stops on 'Resolved pending breakpoint...'
Deploy to Device stops on 'Installed application'
Comment 1 Jeffrey Stedfast 2012-01-30 14:24:29 UTC
Turns out this is because the iOS device/Simulator exits because the FinishedLaunching() method didn't return in 17 seconds.