T O P I C R E V I E W |
wilstark |
Posted - Mar 31 2006 : 1:27:39 PM I've been running DevStudio .NET 2003 for a couple/few years now without seeing this problem. A few months ago I upgraded VAssist to 1440, and now DevStudio seems to leak handles (as reported in Task Manager's 'Handles' column). When the leak reaches 43,000 or so (which takes 1-2 weeks), DevStudio becomes unresponsive and I have to kill it off and restart it. One of my coworkers with VA 1440 and Visual Studio 2005 sees the same symptoms. Have other folks noticed this?
I have thought I should disable VAssist to see the the problem goes away, but I don't know if I could go for a week without it . Does anyone have a suggestion other than this one for how I might determine if VAssist is the cause of the leak?
( A quick test I thought of after the original post: hit the reparse button while a project file is up and watch the handle count go up by 2 each time. Looks like a leak?)
( OK, I've done another test. I've installed VA-X 1444 onto a completely clean Virtual PC install of Visual Studio 2005. Before the VA-X install, you can switch between source files in the DevStudio editor with no increase in the handle count. After the VA-X install, anytime you swtich between source files in the IDE, you see the handle count bump up. You also see the handle count bump up if you press VA-X's reparse current file button. The source files in my "project" were basically just stock C++ files generated by the MFC project wizard. I'm pretty convinced that VA-X is responsible for the handle leak now. Note that disabling and re-enabling VA-X does not recover the handles. )
______________
This information reflects my recent upgrade to 1440:
VA_X.dll file version 10.2.1444.0 built 2006.03.12 Licensed to: <snip> VAOpsWin.dll version 1.3.2.4 VATE.dll version 1.0.4.15 MSDev.exe version 6.0.8168.2 Devshl.dll version 6.0.8798.0 Devedit.pkg version 6.0.8447.0 Comctl32.dll version 5.82.2900.2180 WindowsNT 5.1 Build 2600 Service Pack 2 2 processors
Platform: Win32 (x86) Stable Includes: C:\\Program Files\\Microsoft Visual Studio\\VC98\\INCLUDE; C:\\Program Files\\Microsoft Visual Studio\\VC98\\MFC\\INCLUDE; C:\\Program Files\\Microsoft Visual Studio\\VC98\\ATL\\INCLUDE; d:\\wil\\vc\\mcl\\mcl\\include; D:\\views\\snaplibs\\h2o\\lib\\BOOST_1_30_0; D:\\VIEWS\\SNAPLIBS\\H2O\\MSDDK\\INC;
Library Includes: C:\\Program Files\\Microsoft Visual Studio\\VC98\\MFC\\SRC; C:\\Program Files\\Microsoft Visual Studio\\VC98\\MFC\\INCLUDE; C:\\Program Files\\Microsoft Visual Studio\\VC98\\ATL\\INCLUDE; C:\\Program Files\\Microsoft Visual Studio\\VC98\\CRT\\SRC;
Other Includes:
|
9 L A T E S T R E P L I E S (Newest First) |
support |
Posted - Jun 19 2006 : 5:45:33 PM Fixed in build 1524:
Eliminated handle leak. (case=993) |
feline |
Posted - Jun 06 2006 : 3:14:24 PM it has C++ refactoring, a new and exciting way of introducing bugs into your code soon you will wonder how you ever got by without it |
jpizzi |
Posted - Jun 02 2006 : 5:57:01 PM Probably both |
wilstark |
Posted - Jun 02 2006 : 12:27:21 PM OK. And by "it does contain a lot of additional bugs and features", I'm hoping you really mean "it does contain a lot of additional bug-fixes and features". |
feline |
Posted - Jun 01 2006 : 6:06:44 PM it appears this was only fixed in the 15xx versions of VA, due to the complexity of the change. this version should be going on public beta in the next few days, and it does contain a lot of additional bugs and features, so it is worth checking out. |
wilstark |
Posted - Jun 01 2006 : 11:46:59 AM I have now downloaded 1446 and tried it. It appears that the handle leak is still present |
rhummer |
Posted - Jun 01 2006 : 11:43:20 AM I have you tried 1446 and the leaks are still there?
If they are I assume the change to fix case=993 could not be put out with build 1446. As the fix may conflict with other changes for the 15xx beta builds ( which the leak is fixed ).
Or 1446 was marked incorrectly as a beta build when it shouldn't be? |
wilstark |
Posted - Jun 01 2006 : 11:34:52 AM I see that the next beta is available (1446), yet this change log does not indicate that 993 was fixed. What gives? |
support |
Posted - Mar 31 2006 : 8:56:47 PM Bug will be fixed in our next beta.
case=993
http://forum.wholetomato.com/forum/topic.asp?TOPIC_ID=4365 |