| Author |
 Topic  |
|
|
Heiko Weiss
New Member
3 Posts |
 Posted - Oct 23 2006 : 04:03:14 AM
|
Every times opening a file in the project explorer VANetObj.dll eats 100%Cpu for a very long time.
Output in the status line:
VA X: importing <...>
VA is importing all using <xxx>.
This is very slow.
I have a 2.4 GHz CPU with 1 GB RAM.
VA_X.dll file version 10.3.1539.0 built 2006.10.12
VAOpsWin.dll version 1.3.3.6
VATE.dll version 1.0.5.8
DevEnv.exe version 7.10.6030.0
msenv.dll version 7.10.6030.0
Windows XP 5.1 Build 2600 Service Pack 2
Single processor
|
|
|
feline
Whole Tomato Software
United Kingdom
18948 Posts |
Posted - Oct 23 2006 : 1:37:05 PM
|
this should not be happening, and does not happen for me.
* what programming language are you using?
* can you reproduce this in a different project, or on a different machine?
* do you have any other plugin's installed?
* do you have a localised OS or IDE?
* is there anything "odd" or unusual about your system?
|
zen is the art of being at one with the two'ness |
 |
|
|
Heiko Weiss
New Member
3 Posts |
Posted - Oct 24 2006 : 12:41:01 AM
|
* what programming language are you using?
using C#
* can you reproduce this in a different project, or on a different machine?
yes, it is reproducable in each project.
The more projects in a solution the less is the performance.
We can reproduce this on 3 machines.
The solution where it is very slow contains about 20 Projects.
* do you have any other plugin's installed?
no.
* do you have a localised OS or IDE?
we are using multi language windows XP.
the language running is german.
the ide is in german too (Studio 2003 with SP1).
* is there anything "odd" or unusual about your system?
no.
I even disabled virus scanner etc. still the same.
Cheers
Heiko
|
|
|
|
feline
Whole Tomato Software
United Kingdom
18948 Posts |
Posted - Oct 24 2006 : 1:11:10 PM
|
Do you see this problem in new projects?
Do you have a small sample project that shows this problem?
If you add a new class, or even a new blank .cs file to the project and then restart the IDE and open this new file, do you still see this problem?
Do you have administrator rights on your workstation? If not, which directory is VAX installed into, and do you have rights to write into this directory?
Can you please go to:
VA Options -> About -> Copy Info
and paste the details (from the clipboard) into this thread. This will give us the basic information about your setup. |
zen is the art of being at one with the two'ness |
|
|
|
Heiko Weiss
New Member
3 Posts |
Posted - Oct 25 2006 : 12:40:55 AM
|
*Do you see this problem in new projects?
no, I do not think that this is a problem with the project, but with the count of the projects in the solution and the size of each project.
In our solution we do have 20 projects, the most link to each other.
We have ~ 1200 source files with ~15 MB.
*Do you have a small sample project that shows this problem?
no, small solutions don't have this problems.
We have some small solutions and 2 really big solutions.
with the big sultions we have this problems.
*If you add a new class, or even a new blank .cs file to the project and then restart the IDE and open this new file, do you still see this problem?
nope.
*Do you have administrator rights on your workstation?
sure
*Can you please go to:
*VA Options -> About -> Copy Info
*and paste the details (from the clipboard) into this thread. This *will give us the basic information about your setup.
Here we are:
VA_X.dll file version 10.3.1539.0 built 2006.10.12
Licensed to:
VA X: [email protected] (5-user license) Support ends 2006.12.01
VAOpsWin.dll version 1.3.3.6
VATE.dll version 1.0.5.8
DevEnv.exe version 7.10.6030.0
msenv.dll version 7.10.6030.0
Font: Courier New 13(Pixels)
Comctl32.dll version 5.82.2900.2982
Windows XP 5.1 Build 2600 Service Pack 2
Single processor
Platform: Win32
Stable Includes:
C:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\include;
C:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\atlmfc\\include;
C:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\PlatformSDK\\include\\prerelease;
C:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\PlatformSDK\\include;
C:\\Program Files\\Microsoft Visual Studio .NET 2003\\SDK\\v1.1\\include;
Library Includes:
C:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\atlmfc\\src\\mfc;
C:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\atlmfc\\src\\atl;
C:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\crt\\src;
Other Includes:
|
|
|
|
jpizzi
Tomato Guru
USA
642 Posts |
Posted - Oct 25 2006 : 03:51:18 AM
|
You said that creating a new .cs file does not have the effect. This suggests something in the files that already exist. I wonder if there is one or more using <xxx> lines that is causing the problem?
Could you try adding, one at a time, the most common using <xxx> from your project files to the newly added file, and see if we can discover when/where the performance starts suffering? |
Joe Pizzi |
|
|
|
feline
Whole Tomato Software
United Kingdom
18948 Posts |
Posted - Oct 25 2006 : 1:44:22 PM
|
If you change to an already open file does this happen? I am guessing it does not.
Are the using statements that VA takes a long time to parse for system namespaces, or for ones your company have written?
Assuming that when you open the file "foo.cs" you get the status bar message:
VA X: importing System.Collections
Do you see this same message when you open "bar.cs"? Or are you only seeing this message about new using statements that have not already been parsed?
When you say "VANetObj.dll eats 100%Cpu for a very long time" are you talking 30 seconds? 5 minutes? 30 minutes? |
zen is the art of being at one with the two'ness |
|
|
|
gbozoki
Ketchup Master
USA
70 Posts |
Posted - Oct 25 2006 : 10:57:40 PM
|
I saw this problem, too. At work, we have a huge project (~2500 source files, C#, in 20-something projects.) Running VAX when this solution is open always ends up with me killing the VS process in Task Manager. I normally run VS.Net when I want to work on this project and disable VAX and then open the project. The slowness happens every time without exception on this project. On other, much smaller projects, there is no problem.
Machine and VAX config is pretty much the same as the original poster's, but with 3 GHz dual core processor. |
|
|
|
sean
Whole Tomato Software
USA
2817 Posts |
|
|
Heiko Weiss
New Member
3 Posts |
Posted - Oct 26 2006 : 03:59:24 AM
|
I uninstalled Visual Assist X and completly removed all files in the VAX directory.
Then reinstalled VAX.
Now it seems that it is running faster.
Maybe if editing more and more, it becomes slower again, I'll report here and send the logfiles. |
|
|
|
Heiko Weiss
New Member
3 Posts |
Posted - Oct 26 2006 : 04:18:34 AM
|
one idea:
in our solution we had projects with references to some dll's in a specific directory. These dll where not built in the solution.
Then we removed these dll from the specific directory and added the projects to built this dlls in our solution.
The projects, which referenced these dlls where changed, not to reference to the old dlls in the old directory but reference now to the dlls added to the solution.
You get the picture?
As I remember now, the problems with VAX started after we did that.
Maybe VAX still tried to parse the old dll's?
Or was using an old cache to this dlls?
But as I told before. I removed all from the VAX directory. Since two days it is running fast again. Hope it keeps running fast :)
Thx
Heiko |
|
|
| |
Topic |
|
Slow performance
