Whole Tomato Software Forums - 1530: Parser going crazy (Virtual memory

Whole Tomato Software Forums

User name:	Password:
Save Password
Forgot your password?

All Forums

Visual Assist

Technical Support

1530: Parser going crazy (Virtual memory > 1.5G)

New Topic

Reply to Topic

Printer Friendly

Author

Topic

peterchen
Tomato Guru

126 Posts

Posted - Aug 03 2006 : 05:42:44 AM

I've had a few occurences of the parser going crazy under VS6. Virtual Memory quickly rockets up to 1.2GB .. 1.5GB, and of course everything becomes unresponsive.

Closing VC6 keeps the process active for a long time at peak memory usage (Alwys killed them after 5..10 minutes)

---------------
VA_X.dll file version 10.3.1530.0 built 2006.07.08
Licensed to:
VA X: *********** (1-user license) Support ends 2007.02.26
VAOpsWin.dll version 1.3.3.4
VATE.dll version 1.0.5.7
MSDev.exe version 6.0.8168.2
Devshl.dll version 6.0.8798.0
Devedit.pkg version 6.0.8447.0
Font: ProggyCleanTTSZ 16(Pixels)
Comctl32.dll version 5.82.2900.2180
Windows XP 5.1 Build 2600 Service Pack 2
2 processors

Platform: Custom
Stable Includes:
C:\\DevStudio\\VC98\\INCLUDE;
C:\\DevStudio\\VC98\\MFC\\INCLUDE;
C:\\DevStudio\\VC98\\ATL\\INCLUDE;
d:\\sources\\_Include\\WTL;

Library Includes:
C:\\DevStudio\\VC98\\MFC\\SRC;
C:\\DevStudio\\VC98\\MFC\\INCLUDE;
C:\\DevStudio\\VC98\\ATL\\INCLUDE;
C:\\DevStudio\\VC98\\CRT\\SRC;

Other Includes:
d:\\sources\\Common;
-----------

Repro: Rare. Never happened under VC2005 (but I work mostly on VC6)

It seems to happen a few seconds after I open a file from a fodler I haven't been to for a long time (and which is not part of the project).
I tried to see something under the debugger, but all I could tell oyu is a list of many threads and a few addresses in VA_X.

------------

Not a big issue at the moment (as long as it's called beta

)

Edited by - peterchen on Aug 03 2006 05:44:37 AM

feline
Whole Tomato Software

United Kingdom
19017 Posts

Posted - Aug 03 2006 : 7:06:11 PM

we have had a couple of other reports of similar behaviour, but so far i have not had any problems running 1530 on a fair sized project (over 4,000 files).

certainly any clues you can provide if you run into this more often will be most welcome.

zen is the art of being at one with the two'ness

jpizzi
Tomato Guru

USA
642 Posts

Posted - Aug 04 2006 : 01:08:57 AM

Being VC 6, I would look for a corrupt .ncb file. I think that is what it has been whenever I saw this.

Joe Pizzi

peterchen
Tomato Guru

126 Posts

Posted - Aug 04 2006 : 03:37:22 AM

Just a thought: could you "name" your threads? (http://www.codeproject.com/threads/Name_threads_in_debugger.asp)
That could help prying some information from the call stack without symbols.

Mindcrime
Senior Member

33 Posts

Posted - Aug 22 2006 : 8:34:19 PM

I saw this again with build 1532. I think this is related to me starting 2 instances of VS2005 simultaneously. The 2 instances were maybe fighting with each other and corrupted the VAX data. I deleted the Proj_xxxxxxx directory under vc8 and restarted VS and it seems fine now.