Bug 5360 - [CorDebugger] Pauses in evaluation and timeouts in immediate window
Summary: [CorDebugger] Pauses in evaluation and timeouts in immediate window
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: unspecified
Hardware: PC Windows
: Low normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-05-27 13:21 UTC by Gary____
Modified: 2013-09-16 16:56 UTC (History)
2 users (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:
RESOLVED FIXED

Description Gary____ 2012-05-27 13:21:28 UTC
When on break during debugging, if I go to another method and happen to hover over a variable, the "evaluating..." notice comes up in the popup, as to be expected as that part of the code isnt in the debuggers scope at present. However if I then go back to the method where execution is currently paused, i cant inspect variables for a good period of time (I presume its waiting for the other evaluation to timeout?) and also if I try to execute something in the immediate window it shows Evaluating.... with an increasing number of dots until it returns a result or times out and I need to run it again (often the latter). If I have been to another source window, and allowed it to try and evaluate something, the same happens, this might take longer, but I havn't thoroughly compared them.

This is problematic when you have been referring to other parts of the code to build / copy and paste the statement you wish to execute in the immediate window.

Windows 7, MD 3.0.2
Comment 1 Gary____ 2012-05-27 13:45:05 UTC
These are unit tests run in debug mode as well, in case that makes a
difference.
Comment 2 Marius Ungureanu 2013-09-16 16:56:18 UTC
This is not fixed.
Comment 3 Marius Ungureanu 2013-09-16 16:56:26 UTC
This is now fixed. *