Bug 4866 - parameter locals are not resolved on newly opened files
Summary: parameter locals are not resolved on newly opened files
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Text Editor ()
Version: Trunk
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Mike Krüger
: 4888 5321 ()
Depends on:
Reported: 2012-05-03 16:29 UTC by Mikayla Hutchinson [MSFT]
Modified: 2012-05-25 11:48 UTC (History)
3 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 Mikayla Hutchinson [MSFT] 2012-05-03 16:29:51 UTC
The semantic highlighting engine sometimes does not resolve parameter locals on newly opened files.
Comment 1 Mike Krüger 2012-05-04 04:42:58 UTC
hm, I've done some lazy loading additions yesterday - I bet there is a connection here.

Unfortunately I don't see a way to write tests for these things (thread racing is involved here). Fortunately it's very easy to see the red things :)
Comment 2 Mikayla Hutchinson [MSFT] 2012-05-04 15:34:03 UTC
*** Bug 4888 has been marked as a duplicate of this bug. ***
Comment 3 Mike Krüger 2012-05-05 06:34:36 UTC
Should work now again - reopen if it still persists.
Comment 4 Mikayla Hutchinson [MSFT] 2012-05-08 18:28:46 UTC
Still seeing this occasionally on master.
Comment 5 Mike Krüger 2012-05-09 01:13:50 UTC
fixed a potential cause.
Comment 6 Mikayla Hutchinson [MSFT] 2012-05-25 11:48:00 UTC
*** Bug 5321 has been marked as a duplicate of this bug. ***