| T O P I C R E V I E W |
| wilstark |
Posted - Sep 13 2006 : 7:49:42 PM
I was just editing along, switched to a different file (an .idl file), and I get the hourglass for many minutes before VS2003 comes back. Attaching VS2005 to my VS2003 to debug shows VA_X.dll in the callstack:
> VA_X.dll!1ee5fbbc()
[Frames below may be incorrect and/or missing, no symbols loaded for VA_X.dll]
VA_X.dll!1ee57259()
VA_X.dll!1ed0ef62()
VA_X.dll!1ed0fe6c()
VA_X.dll!1ee553bc()
VA_X.dll!1ee6fc90()
VA_X.dll!1eddf242()
VA_X.dll!1edde57c()
VA_X.dll!1ed10167()
VA_X.dll!1eddf242()
VA_X.dll!1ed10167()
VA_X.dll!1eddf242()
VA_X.dll!1ed10167()
VA_X.dll!1eddf242()
VA_X.dll!1ed10167()
VA_X.dll!1eddf242()
VA_X.dll!1ed10167()
VA_X.dll!1eddf242()
VA_X.dll!1ed10167()
VA_X.dll!1eddf242()
VA_X.dll!1ed10167()
VA_X.dll!1eddf242()
VA_X.dll!1ed10167()
VA_X.dll!1eddf242()
VA_X.dll!1ed10167()
VA_X.dll!1eddf242()
VA_X.dll!1ed10167()
kernel32.dll!_InitializeCriticalSection@4() + 0xe bytes
VA_X.dll!1ed0e9de()
VA_X.dll!1ed72495()
VA_X.dll!1ed79e21()
ntdll.dll!_RtlAllocateHeap@12() + 0x117 bytes
ntdll.dll!_RtlpFreeToHeapLookaside@8() + 0x26 bytes
ntdll.dll!_RtlFreeHeap@12() + 0x130 bytes
203b0006()
Build 1533 didn't seem to have this problem - or maybe it did and I never saw it. I ran 1533 for a couple weeks without problems. I've been running 1534 for about a day. This has happened twice now, both times when I switched to my IDL file to edit. I made a couple changes (like type a few characters), and then it hangs up. CPU usage for devenv.exe 100% (50% of one processor) during this time. If I'd not taken the time to attach the debugger the first time (I have a .dmp file), I would have assumed that it was gone forever after a few minutes and killed off devenv.exe - but then it came back after 5-10 minutes or so. I assume it must be off parsing something using all that CPU (?)
(It's now been 10 minutes since the 2nd hangup, and devenv has still not recovered, so even though it came back the first time, I'm not waiting anymore... I did create a 2nd .dmp file.)
Here's my VA-X info:
VA_X.dll file version 10.3.1534.0 built 2006.09.02
Licensed to:
VA X: [email protected] (17-user license) Support ends 2006.12.02
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:
|
| 5 L A T E S T R E P L I E S (Newest First) |
| wilstark |
Posted - Sep 14 2006 : 12:48:23 PM
I reproduced the problem with logging on, and have mailed the log file and the .idl file to support.
I removed the unicode chars yesterday after realizing they were there, and have not had a problem since then. You can draw your own conclusions on that one  |
| support |
Posted - Sep 14 2006 : 10:04:45 AM
Looking at the stack we can see where the problem, but cannot see why it happened. Can you enable logging on the performance tab of the VA options dialog, reproduce the problem then zip and send us the log c:\\va.log?
Any chance you can send the IDL file to Support? |
| rhummer |
Posted - Sep 13 2006 : 8:20:45 PM
have you tried removing the unicode comment form the file and seening if it happens again? |
| wilstark |
Posted - Sep 13 2006 : 8:16:42 PM
Don't know if this might be related, but I found that a couple Unicode characters had gotten into the .idl file in question (in a // comment) at some time in the past. Looks like someone pasted a comment from some other editor (Word, maybe) with the special back-double-quote and forward-double-quote in it. |
| wilstark |
Posted - Sep 13 2006 : 8:01:33 PM
After restarting VS2003, I reproduced this again very quickly. Interestingly, it went out to lunch for 10 seconds or so and then came back. Then a few seconds later it went into the seemingly permanent hang state before a killed it off again. |
