| T O P I C R E V I E W |
| wilstark |
Posted - Oct 02 2006 : 7:36:21 PM
In a few seconds, the system comes to a thrashing crawl as VS's memory footprint exceeds the RAM in my box.
I opened a file, say X.cpp, then open another copy (earlier revision), then used my keyboard shortcut go to the VA-X find-method drop down, type the name of the routine I'm looking for - hit backspace since I mistype (not sure if this is required), and at some point right there I can say "see-you-later environment" as memory allocation for devenv shoots up from 500MB to 1.5GB in a few secs. Then things start to slow down as thrashing really kicks in. I repeated this several times, and captured a log file of the last time. Should I send this in?
- Wil
VA_X.dll file version 10.3.1535.0 built 2006.09.15
Licensed to:
<snip>
VAOpsWin.dll version 1.3.3.6
VATE.dll version 1.0.5.8
DevEnv.exe version 7.10.3077.0
msenv.dll version 7.10.3077.0
Font: Courier New 13(Pixels)
Comctl32.dll version 5.82.2900.2180
Windows XP 5.1 Build 2600 Service Pack 2
2 processors
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;
d:\\views\\snaplibs\\h2o\\lib\\boost_1_33_1;
d:\\views\\snaplibs\\h2o\\lib\\mcl\\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;
z:\\h2o\\src\\Projects;
Other Includes:
|
| 2 L A T E S T R E P L I E S (Newest First) |
| jpizzi |
Posted - Oct 02 2006 : 11:10:00 PM
Even though it has disappeared, logfiles should be sent to [email protected].
You might consider (if you still have it around) sending in the logfile that you have, to see if there is anything there that might help avoid this in the future. |
| wilstark |
Posted - Oct 02 2006 : 8:00:37 PM
Update - all I have to do is open the second file and apparently upon parsing it, VA-X gets into its allocation loop. The fact that I was using the find-method drop-down right after opening the file is apparently unrelated.
I tried telling it to rebuild symbol databases and clear cache files, and now the problem seems to have disappeared.
- Wil |
|
|
