Bug 4796 - deadlock with threads
Summary: deadlock with threads
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
Depends on:
Reported: 2012-05-01 09:28 UTC by Sebastien Pouliot
Modified: 2013-12-05 18:36 UTC (History)
2 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 Sebastien Pouliot 2012-05-01 09:28:07 UTC
This happens (at least) on iOS devices and simulator.

Add a test case, like this one:

	public void X ()
		Parallel.For (0, 128, delegate (int arg1, ParallelLoopState arg2) {
				Y ();

	public void Y ()
		Assert.True (true);

and it works correctly (like expected) once executed.

Now set a breakpoint on `Y ()` (inside X) or inside Y. The breakpoint will be hit the first time then, if you resume exection, the breakpoint won't be hit again (bad) and the execution won't ever end (worse).

Only removing the breakpoint will let the loop finish it's execution normally.
Comment 1 Mikayla Hutchinson [MSFT] 2012-05-01 14:09:27 UTC
When you press "resume", does the stack pad show a stack trace?
Comment 2 Mikayla Hutchinson [MSFT] 2012-05-01 14:12:04 UTC
It sounds like the app is hissting another breakpoint - maybe it stopped on the same breakpoint on multiple threads and is dequeuing - but not displaying the status correctly. So what I'm asking is really - is it just the tet editor that's not displaying "broken" status correctly, or is it the pads too?
Comment 3 PJ 2013-11-19 17:05:46 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 4 PJ 2013-12-05 18:36:14 UTC
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.

Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.