- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
After I have updated my IVF instance to update 7, I have noticed that after I open my solution (which is fairly large) that Visual Studio takes up 100% of my CPU for a few minutes at load time (2.5 minutes - 3.5 minutes) during which it seems to be parsing/scanning every source file present in my project (multiple times for those files included as parts of multiple projects). The solution opens successfully in the end, and I don't see any ill effects, but this behavior is markedly different then what I experienced using Update 4 previously.
I know previous posts I have read have indicated that Update 7 did a rework of how the source code/intellisense integration worked under Visual Studio, I just wanted to know if this is the default behavior, or if there is something amiss with my project? As always, thanks for the feedback.
I know previous posts I have read have indicated that Update 7 did a rework of how the source code/intellisense integration worked under Visual Studio, I just wanted to know if this is the default behavior, or if there is something amiss with my project? As always, thanks for the feedback.
Link Copied
5 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Matt,
To support Object Browser and intellisense features, we scan all files in all projects included into solution. If some of common files are included in several projects, these files are scanned in the context of each project. For very large projects it may take a long time, but should not interfere because runs in the background.
Is this running in the background for you or in the foreground and preventing you from using Visual Studio until it finishes?
To support Object Browser and intellisense features, we scan all files in all projects included into solution. If some of common files are included in several projects, these files are scanned in the context of each project. For very large projects it may take a long time, but should not interfere because runs in the background.
Is this running in the background for you or in the foreground and preventing you from using Visual Studio until it finishes?
------
Wendy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I had similar results after the update too, but it seemed it worked better on my other pc. I would love to see a solution too. It used indeed 100% of cpu, altough nothing heavy was loaded.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Wendy, it is running in the background after my solution opens (although, given how old and slow my computer is, running in the background/foreground don't make huge differences ;) ). Like I said, it doesn't seem to impact anything, it was just a different behavior that I wasn't expecting. Thanks for the answer.
Could I offer up a request/suggestion for future updates though? If possible, can the scanning process cache its results (after it does a full scan the first time a program opens) and only scan for files that have changed since the last pass when opening projects/solutions?
Could I offer up a request/suggestion for future updates though? If possible, can the scanning process cache its results (after it does a full scan the first time a program opens) and only scan for files that have changed since the last pass when opening projects/solutions?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the suggestion. I have submitted this as a feature request and will update this thread when we it is implemented or needs more information. Others can post to this thread and will add your names to the feature request.
The engineering ID is: DPD200176168
Thanks,
------
Wendy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This bug was addressed in the 15.0 compiler, aka Composer XE 2015
Ron

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page