Build 1559 crashes VS2008 when you type cntrl-f

I've noticed this in all of the various recent builds including the latest (at this point) 1559. If I have source code open and type cntrl-f the Find box appears and within a few seconds I will see the "Need to restart Visual Studio" dialog. I am using VS2008 Standard along with the AnkhSVN plug-in.

8 comments
Comment actions Permalink

please look to this topic:

http://www.jetbrains.net/devnet/thread/285719?tstart=0

and follow my commands to get a dump and open it with WinDbg

0
Comment actions Permalink

Pardon my ignorance but can you tell me where I can find the adplus.vbs script mentioned in that thread? You said in the 'windows debugger tools' but I'm not sure what that means. I did a search of my Program Files folder and could not locate it as part of my VS2008/.Net installs. Thanks.

0
Comment actions Permalink

Still seeing this in bld 1571. Any feedback to my previous question would be welcome so that I can get the required information to diagnose this. It's really a giant pain to not have cntrl-f functionality.

Thnx.

0
Comment actions Permalink

Hello,

Still seeing this in bld 1571. Any feedback to my previous question
would be welcome so that I can get the required information to
diagnose this. It's really a giant pain to not have cntrl-f
functionality.


Are you running a 64-bit WinXP machine?


Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”


0
Comment actions Permalink

Yes. Windows XP x64.

0
Comment actions Permalink

Hello,

Yes. Windows XP x64.


I do not quite remember the details of the case, but this was identified
to be the cause — an problem in WoW6432 implementation in this operating
system. In short, 64-bit support in WinXP was not quite mature yet in respect
of running 32-bit applications in 32-bit emulation mode (which applies to
Visual Studio process). Many things were fixed in later SPs and updates,
so that's the first thing to check — whether all related critical and optional
Windows Updates are installed on top of the latest Service Pack.


Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”


0
Comment actions Permalink

Hello Serge,

As far as I remember, the problem was that the fix was QFE not included in
Windows Update fixes. See http://resharper.blogspot.com/2007/12/resharper-and-visual-studio-crash-on.html

Sincerely,
Ilya Ryzhenkov

JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


SB> Hello,
SB>
>> Yes. Windows XP x64.
>>
SB> I do not quite remember the details of the case, but this was
SB> identified to be the cause — an problem in WoW6432 implementation in
SB> this operating system. In short, 64-bit support in WinXP was not
SB> quite mature yet in respect of running 32-bit applications in 32-bit
SB> emulation mode (which applies to Visual Studio process). Many things
SB> were fixed in later SPs and updates, so that's the first thing to
SB> check — whether all related critical and optional Windows Updates
SB> are installed on top of the latest Service Pack.
SB>
SB> —
SB> Serge Baltic
SB> JetBrains, Inc — http://www.jetbrains.com
SB> “Develop with pleasure!”


0
Comment actions Permalink

Thanks, that Hot Fix did the trick!

-Noah

0

Please sign in to leave a comment.