| T O P I C R E V I E W |
| meissnersd |
Posted - Jun 25 2008 : 08:35:19 AM
I just upgraded to 1640 and VS started crashing hard.
I have a dual install of VS2008 and VS2005 SP1 on WinXp x64. After I installed this morning, as soon as I click on "Find In Files..." from the VS Edit Menu in VS2008 it crashes, offers to send a report to Microsoft and then restarts VS2008.
It seems to work ok in VS2005.
Do you need a log dump to help with the a fix?
It reproduces every time...
If not, how can I revert to an older build with out this issue so I can wait for a patch....
Karl |
| 17 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Jul 11 2008 : 1:46:18 PM
I have the dump file, thank you for this:
case=18412 |
| feline |
Posted - Jul 07 2008 : 08:18:24 AM
When the IDE crashes, are you able to debug this crash with a second IDE instance? I am wondering if you can get a mini dump file. A mini dump and matching log files would be very helpful, and might help to explain what is causing these problems.
If you can collect these please submit the files via the form:
http://www.wholetomato.com/support/contact.asp
including this thread ID or URL in the description, so we can match it up.
Clearly something is going on here, but what? Since the crash frequency seems to depend on the version of VA it does seem that VA is a factor. |
| mnd |
Posted - Jul 07 2008 : 04:06:01 AM
Hi,
Since I could not stop those crashes on 1640 i reverted back to 1635 for the whole week, since them I had very few crashes, 1 or 2 a week instead of the 5-6 each day. Those crashes happen in the same way, just running the debugger. I have to say that I never experienced those kind of crashes until I upgraded to 1635, with 1640 they are more or less systematic.
Today, working with 1635, I had a strange bug where I could not edit the file anymore, I disable VA and reanabled but then I could not disable VA anymore (the option in the menu was not highlighet) even if the menu's was showing that VA was enabled.
I close the solution without problems and When I close the IDE I got a message box from Visual Studio that tells me that VA caused an exception. I took a screenshot of it.
So I decided to give 1640 another try, I reinstalled it, I enabled the logs, tried to run the debugger and I had another crash.
Va.log was empty.
Vassist.lo contains something like:
....
BeforeExecute {
BeforeExecute2 {
Debug.Start
} BeforeExecute2
} BeforeExecute
VAM_GETSEL {
} VAM_GETSEL
DLLMain {
} DLLMain
....
WM_SETTEXT {
} WM_SETTEXT
AfterExecute {
Debug.Start
VA_CurrentWnd {
} VA_CurrentWnd
} AfterExecute
VAM_SETCURDOCOBJ {
} VAM_SETCURDOCOBJ
VAM_GETSEL {
} VAM_GETSEL
DLLMain {
} DLLMain
....
VAM_GETSELSTRING {
} VAM_GETSELSTRING
VAM_GETSEL {
} VAM_GETSEL
VAM_GETSEL {
} VAM_GETSEL
VAM_GETSEL {
} VAM_GETSEL
VAM_GETSEL {
} VAM_GETSEL
VAM_GETSEL {
} VAM_GETSEL
VAM_GETSEL {
} VAM_GETSEL
VAM_GETSEL {
} VAM_GETSEL
DLLMain {
} DLLMain
I took you suggestion and I replaced the ncb with an empty one read only.
Does it help in any way?
What I can do to help you narrow down the problems?
Do you need the screenshot I was talking about?
Do you need the logs?
regards,
- mn |
| feline |
Posted - Jun 30 2008 : 3:10:41 PM
Have you installed the Microsoft hotfix mentioned here?
http://docs.wholetomato.com?W308
https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=311712 |
| ted |
Posted - Jun 27 2008 : 3:18:42 PM
With XP64 Service Pack 2, build 1640 and latest Visual Studio I have the same problem with find or ctrl+f. If I take Visual Assist out of the add-ins I have now failure.
My system is completely uptodate with patches and drivers.
When I retreated to build 1626 the issue went away. I found the problem in the latest prior beta releases as well. So it seems that the new code introduced the problem.
I can also wait for a patch as I reverted to the original code base |
| feline |
Posted - Jun 27 2008 : 10:39:41 AM
I am not seeing any sign of VA in the call stack.
Can you try closing the IDE and deleting your NCB file please. This is stored in the root directory of the solution. I have often seen a corrupt NCB file crash VS2003, even without having VA installed. I used to replace the NCB file with a zero length read only file to avoid this problem.
If we are lucky this will stop the crashes. |
| mnd |
Posted - Jun 27 2008 : 04:19:50 AM
Well, today I had a crash without doing any find in files...
the exception is:
Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\\devenv.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available
Symbol search path is: SRV*%TEMP%\\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: SingleUserTS
Debug session time: Fri Jun 27 09:44:07.000 2008 (GMT+2)
System Uptime: not available
Process Uptime: 0 days 1:00:19.000
.....................................................................................................................................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(bb4.960): Access violation - code c0000005 (first/second chance not available)
eax=fff75e3b ebx=0d8c27cc ecx=0c980d50 edx=547afa08 esi=0d8c27e8 edi=fff75e3b
eip=54723344 esp=0fe5eec4 ebp=0fe5ef28 iopl=0 nv up ei ng nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000282
NatDbgDE!CSymbolHandler::GetErrorMessage+0x13:
54723344 ff348568337254 push dword ptr NatDbgDE!`string'+0x14 (54723368)[eax*4] ds:0023:544fac54=????????
and the stack:
NatDbgDE!CSymbolHandler::GetErrorMessage+0x13 (FPO: [2,0,0])
NatDbgDE!CModule::Load+0x186 (FPO: [Non-Fpo])
NatDbgDE!CNativeProcess::NotifyModLoad+0x8b (FPO: [Non-Fpo])
NatDbgDE!CNativeProcess::Callback+0x200 (FPO: [Non-Fpo])
NatDbgDE!OSDDoCallBack+0x23 (FPO: [Non-Fpo])
NatDbgDE!EMCallBackDB+0xa0 (FPO: [Non-Fpo])
NatDbgDE!LoadFixups+0x1fa (FPO: [Non-Fpo])
NatDbgDE!DebugPacket+0x37d (FPO: [Non-Fpo])
NatDbgDE!EMFunc+0x2bd (FPO: [Non-Fpo])
NatDbgDE!TLCallBack+0x29 (FPO: [Non-Fpo])
NatDbgTLLoc!DMTLFunc+0x4c (FPO: [Non-Fpo])
NatDbgDM!DMSendPacket+0x10a (FPO: [Non-Fpo])
NatDbgDM!NotifyEM+0x42f (FPO: [Non-Fpo])
NatDbgDM!ProcessLoadDLLEvent+0x33 (FPO: [Non-Fpo])
NatDbgDM!ProcessDebugEvent+0x2f1 (FPO: [Non-Fpo])
NatDbgDM!DmPollLoop+0x3a (FPO: [Non-Fpo])
msvcr71!_endthreadex+0xa0 (FPO: [Non-Fpo])
kernel32!BaseThreadStart+0x37 (FPO: [Non-Fpo])
I can't understand why it is crashing, but I started to see those kind of crashes after having upgrade to VA1640...
Do you have any hints?
regards,
- mn |
| mnd |
Posted - Jun 27 2008 : 01:21:20 AM
it becomes really hard to work without VA... :-)
Anyway I'll try. |
| feline |
Posted - Jun 26 2008 : 5:58:06 PM
Does the crash go away if you disable VA?
There seems to be an inherent crash problem with Find in Files in the IDE, independent of VA. |
| mnd |
Posted - Jun 26 2008 : 10:14:38 AM
I'm sorry, I can see now that my situation is different.....I have the crash after when I start the debugger but only after having done a "find in files".
Windows XP 5.1 Build 2600 Service Pack 3
32bit.
|
| feline |
Posted - Jun 26 2008 : 09:51:41 AM
mnd do you have a 32bit or 64bit OS?
If you have a 64bit OS then can you try the Microsoft hot fix? |
| mnd |
Posted - Jun 26 2008 : 04:37:53 AM
I've the same problem on Visual Studio 2003, after the upgrade to 1640 in the last 2 days I had 8 crashes when doing "find in files".
Also a lock sometimes occur when doing "find in files" and VAx wants to reparse the same file being searched on (altough it happens rarely, mostly when the machine is under heavy load and VAx takes more time to parse a file).
VA_X.dll file version 10.4.1640.0 built 2008.05.22
Licensed to:
VA X: xxxxxxxxxxxx (1-user license) Support ends 2009.05.12
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.5512
Windows XP 5.1 Build 2600 Service Pack 3
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;
Other Includes:
Stable Source Directories:
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;
|
| meissnersd |
Posted - Jun 25 2008 : 6:03:55 PM
ok thanks |
| feline |
Posted - Jun 25 2008 : 5:43:12 PM
This is true. From the page the FAQ links to:
quote:
WeG??ve heard of Ultramon, NVidia drivers and Logitech drivers triggering the issue G?? all these apps globally hook Windows messages. (To be clear, the issue doesnG??t sit with these 3rd party apps.)
I have no idea about the time scale for that SP. |
| meissnersd |
Posted - Jun 25 2008 : 3:13:43 PM
This
http://msdn.microsoft.com/en-us/vstudio/products/cc533447.aspx
says that it they have a hot fix but that it should also be fixed in VS2008 SP1. I guess I rather put on the whole service pack. It looks like that is still in beta. Any idea when they are going to RTM with the service pack? |
| feline |
Posted - Jun 25 2008 : 11:28:10 AM
You may be seeing this problem:
http://docs.wholetomato.com?W308
which is caused by a bug in Windows its self, and Microsoft has produced a patch for this problem. |
| Feasoron |
Posted - Jun 25 2008 : 11:19:57 AM
As of this morning when I ran the update, I am also seeing a crash during Find in Files. |
