| Author |
 Topic  |
|
|
Jaeyoun Yi
New Member
9 Posts |
 Posted - Jun 14 2006 : 01:23:44 AM
|
Hi, all. I'm a licensed user of Visual Assist X.
In my office, there are 3 developers who are using VA-X with VS2005.
And the other 2 developers are not using VA-X.
In the system on which VA-X is installed, VS2005 goes to hang when closing VS2005 IDE, for some solution files.
If I close the solution right after opening the solution without building, then no problem. However, if I build the solution once, then the IDE goes to hang when closing the solution.
Disabling VA-X before closing the solution does not make any difference.
The problem occurs only in VA-X users' computer. Without VA-X installed, no problem.
Do you have any idea?
|
|
|
bugfix
Tomato Guru
Germany
324 Posts |
|
|
feline
Whole Tomato Software
United Kingdom
18939 Posts |
Posted - Jun 14 2006 : 6:15:27 PM
|
can you load a second copy of the IDE and use it to get a call stack next time this happens?
are there any other plugin's installed?
is there any pattern to this hang? does it happen every time, or only some of the time?
as a wild guess, does deleting the ncb file for the solution make any difference? these are prone to getting corrupt in the earlier IDE's, and when they are corrupt the IDE can crash. |
zen is the art of being at one with the two'ness |
 |
|
|
Jaeyoun Yi
New Member
9 Posts |
Posted - Jun 15 2006 : 12:37:25 AM
|
To bugfix:
Thank you for your reply.
I knew that whole-tomato announce the localized VS is not supported. But up to now incuding VS2003, VA-X has been working perfectly.
I tried to close my IDE after disabling VAX in Tools->Add-in Manager. Then the IDE crashed, not hanged.
To feline,
Thanks for your reply.
In Add-in manager, I can see only two plugins, VAX and AMD Code Analysist. But I don't think AMD code-analysist is the reason.
As I described in the previous post, this hang always happend when the IDE opens "some solution files" and build them.
Before building the solution, then no problem.
In 'some solution files', it happens all the time. But for the others, no problem at all.
And deleting the ncb file does not make difference.
As for the call-stack, do you want to see the call-stack of the IDE?
If so, the call stack is as follows:
> mscorlib.dll!System.Threading.WaitHandle.WaitAny(System.Threading.WaitHandle[] waitHandles, int millisecondsTimeout, bool exitContext) + 0x63 bytes
System.dll!System.Net.TimerThread.ThreadProc() + 0x246 byte
mscorlib.dll!System.Threading.ThreadHelper.ThreadStart_Context(object state) + 0x3b byte
mscorlib.dll!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state) + 0x81 byte
mscorlib.dll!System.Threading.ThreadHelper.ThreadStart() + 0x40 byte
|
|
|
|
Jaeyoun Yi
New Member
9 Posts |
Posted - Jun 15 2006 : 12:44:37 AM
|
Ooops!
Diabling VAX in Add-in manager always crashes IDE !! What's the problem?
|
|
|
|
feline
Whole Tomato Software
United Kingdom
18939 Posts |
Posted - Jun 15 2006 : 6:01:23 PM
|
can you try disabling the AMD code-analysist plugin to see if it makes a difference. in order to work VA has to hook into the IDE all over the place, so strange things can and do happen with other plugins.
i will ask support and see if they have any ideas on this. |
zen is the art of being at one with the two'ness |
|
|
|
jpizzi
Tomato Guru
USA
642 Posts |
Posted - Jun 16 2006 : 02:02:42 AM
|
The crash when you disable VA is a known problem.
case=1167
It is, however, very low on the list of items to fix. I have asked if there is a known workaround. Will let you know. |
Joe Pizzi |
|
|
|
jpizzi
Tomato Guru
USA
642 Posts |
Posted - Jun 16 2006 : 09:24:40 AM
|
To disable VA manually, you can use Regedit or a script to change the following registry value:
HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\8.0\\Addins\\VAssistNET.Connect8
To disable set value of LoadBehavior to 0.
To enable set value of LoadBehavior to 1.
Please note that you need to do this when the IDE is not running. |
Joe Pizzi |
|
|
|
Jaeyoun Yi
New Member
9 Posts |
Posted - Jun 26 2006 : 04:23:06 AM
|
Thank you jpizzi.
I tested the case after disabling VAX according to your post.
My test procedure is:
Disabling VAX in regedit --> Opening the solution in VS2005 --> Build --> Close IDE.
Then, the IDE always goes to crash...
Now I think it's not a VAX isssue...
Do you have any idea? |
|
|
|
feline
Whole Tomato Software
United Kingdom
18939 Posts |
Posted - Jun 26 2006 : 4:19:09 PM
|
a long shot, you could try deleting any ncb files you have. in VS2003 these can get corrupt, and cause the IDE to crash. the IDE simply rebuilds these files if you delete them. there is normally one per solution, in the solution base directory.
you may want to uninstall VA, and see if the IDE still crashes.
how easy is it to reinstall both VA and the AMD code analysis plugin? if it is quick it may be worth a try, to see if that helps. |
zen is the art of being at one with the two'ness |
|
|
|
Jaeyoun Yi
New Member
9 Posts |
Posted - Jun 28 2006 : 10:28:34 PM
|
Deleting ncb files does not affect this problem.
Today, I had to reinstall the windows on my system, so I could test this problem clearly.
After installing VS2005 right after installing windows (xp64), there's no prbolem in the above.
No hang nor crash when closing the IDE, even after building the solution.
Next I installed the latest VAX and opened the solution and built it. Then, VS2005 hangs when closing the IDE.
Disabling VAX (using registry tweak) cause crashes.
Anyway, there are two more developers in my office, who are suffering from the same problem.
Haven't you guys here ever experienced it?
Then, I guess it may be related to Korean-localized version of VS2005 only.
|
|
|
|
feline
Whole Tomato Software
United Kingdom
18939 Posts |
Posted - Jul 01 2006 : 4:55:40 PM
|
it is possible the localised IDE is a factor. is it possible for you to get a call stack of the hung IDE? hopefully that might give us some clues. the other thing to try is to turn on VA logging before closing the IDE, so we can get a log.
http://www.wholetomato.com/support/faq.html#log
does your machine have multiple processors? |
zen is the art of being at one with the two'ness |
|
|
|
support
Whole Tomato Software
5566 Posts |
Posted - Jul 02 2006 : 2:57:37 PM
|
Unloading VA X, or many other complex add-ins, while running within VS2005 does cause the IDE to crash. This is why we recommend only to disable "at startup." (Unloading a complex add-in about which the IDE knows so little is quite traumatic.)
Your test case on the new Windows install seems very clean. (We appreciate your effort.)
Can we assume the other add-in, AMD code analysis, was not yet installed?
What build of VA X do you have? (We don't seem to know from this thread.) If not already, can you try build 1528?
http://www.wholetomato.com/downloads/VA_X_Setup1528.exe |
|
|
|
Jaeyoun Yi
New Member
9 Posts |
Posted - Jul 04 2006 : 03:57:06 AM
|
Thank you all.
To feline:
The call stack of the hung IDE was in the above. (The 3rd reply).
I'll try VA logging soon.
And my system has a Dual-Core CPU (AMD Athlon64 X2 4200+).
But one of users in my office is runnig VAX on Single CPU (Intel Pentium4) system and he is suffering from same problem.
To support:
My VAX version is 10.2.1446.0 (built 2006.5.31)
I'll try 1528 later too.
|
|
|
|
Jaeyoun Yi
New Member
9 Posts |
Posted - Jul 04 2006 : 04:07:40 AM
|
Logs from build 1445 are as follows:
Startup.log
EDL::149 7/4/2006 17:04:52 0x1474
EDL::167 7/4/2006 17:04:52 0x1474
EDL::173 7/4/2006 17:04:57 0x1474
TI: 5-:213 7/4/2006 17:04:57 0x1474
EDL: , 5, :227 7/4/2006 17:04:57 0x1474
EDL::279 7/4/2006 17:04:57 0x1474
EDLck Load::797 7/4/2006 17:04:57 0x1474
EDLck Locked::1765 7/4/2006 17:04:57 0x1474
EDLck Load::827 7/4/2006 17:04:57 0x1474
EDLck UnLocked::1790 7/4/2006 17:04:57 0x1474
EDLck Locked::1765 7/4/2006 17:04:58 0x19ec
EDLck Load::797 7/4/2006 17:04:58 0x19ec
EDLck Load::827 7/4/2006 17:04:59 0x19ec
EDLck UnLocked::1790 7/4/2006 17:05:02 0x19ec
va.log
Logfile created - level 7(0x00000007) PID 5132(0x0000140c)
VA_X.dll file version 10.2.1446.0 built 2006.05.31
Licensed to:
VA X: [email protected] (3-user license) Support ends 2007.03.14
VA.NET 7.1:
VAOpsWin.dll version 1.3.2.4
VATE.dll version 1.0.4.14
DevEnv.exe version 8.0.50727.42
msenv.dll version 8.0.50727.42
Font: -?-+-++?+?-+ 13(Pixels)
Comctl32.dll version 6.0.3790.1830
WindowsNT 5.2 Build 3790 Service Pack 1
2 processors
(31 s)
VAssist.log
} VAM_EXECUTECOMMAND
} BeforeExecute2
} BeforeExecute
AfterExecute {
VisualAssistX.Options
VA_CurrentWnd {
} VA_CurrentWnd
} AfterExecute
QueryStatus {
NeededText {
} NeededText
VA_CurrentWnd {
} VA_CurrentWnd
} QueryStatus
BeforeExecute {
BeforeExecute2 {
Build.BuildSolution
} BeforeExecute2
} BeforeExecute
AfterExecute {
Build.BuildSolution
VA_CurrentWnd {
} VA_CurrentWnd
} AfterExecute
DLLMain {
} DLLMain
BeforeExecute {
BeforeExecute2 {
Edit.GoToFindCombo
} BeforeExecute2
} BeforeExecute
VA_CurrentWnd {
} VA_CurrentWnd
BeforeExecute {
BeforeExecute2 {
Edit.GoToFindCombo
} BeforeExecute2
} BeforeExecute
BeforeExecute {
BeforeExecute2 {
Build.SolutionConfigurations
} BeforeExecute2
} BeforeExecute
BeforeExecute {
BeforeExecute2 {
Build.SolutionConfigurations
} BeforeExecute2
} BeforeExecute
BeforeExecute {
BeforeExecute2 {
Build.SolutionPlatforms
} BeforeExecute2
} BeforeExecute
BeforeExecute {
BeforeExecute2 {
Build.SolutionPlatforms
} BeforeExecute2
} BeforeExecute
BeforeExecute {
BeforeExecute2 {
Edit.GoToFindCombo
} BeforeExecute2
} BeforeExecute
BeforeExecute {
BeforeExecute2 {
CallBrowserSearch
} BeforeExecute2
} BeforeExecute
BeforeExecute {
BeforeExecute2 {
CallBrowserSearch
} BeforeExecute2
} BeforeExecute
BeforeExecute {
BeforeExecute2 {
Showoutputfrom
} BeforeExecute2
} BeforeExecute
BeforeExecute {
BeforeExecute2 {
Showoutputfrom
} BeforeExecute2
} BeforeExecute
BeforeExecute {
BeforeExecute2 {
Showoutputfrom
} BeforeExecute2
} BeforeExecute
BeforeExecute {
BeforeExecute2 {
File.Exit
} BeforeExecute2
} BeforeExecute
AfterExecute {
File.Exit
VA_CurrentWnd {
} VA_CurrentWnd
} AfterExecute
DLLMain {
} DLLMain
Error caught in VSMsg2: 0 (0x1055, 0x0, 0x0)
DLLMain {
} DLLMain
|
|
|
|
Jaeyoun Yi
New Member
9 Posts |
Posted - Jul 04 2006 : 04:15:00 AM
|
| I tried 1528, but no difference. |
|
|
|
Jaeyoun Yi
New Member
9 Posts |
Posted - Jul 25 2006 : 7:23:39 PM
|
Hi, all.
No more information on this issue? |
|
|
|
feline
Whole Tomato Software
United Kingdom
18939 Posts |
Posted - Jul 30 2006 : 5:55:41 PM
|
| i have just emailed support again about this one, in the hope they will be able to make some sense of this. |
zen is the art of being at one with the two'ness |
|
|
|
support
Whole Tomato Software
5566 Posts |
Posted - Jul 31 2006 : 8:47:18 PM
|
Your call stack includes .NET managed code which cannot be from VA X. (VA X doesn't have any.)
Is there anything in common with the solutions that cause the crash on exit? Are they C#? Managed C?
Can you disable "at startup" the AMD code analysis add-in? While you don't think there should be conflict, sometimes it happens anyhow, and at exit is a common place for a conflict to occur. |
|
|
| |
Topic |
|
Is it a VA-problem?
