ReSharper under XP 64

When loading VS.net I get a crash from ReSharper, invalid pointer. The AddIn then disables itself but it has then trashed VS. From then on when I load a solution or even create an empty one then add a project the moemory goes through the roof until crashing. I had to reinstall XP64 to get it working again as simply removing VS and reinstalling didnt fix it! Anyone else had similar problems? Luckily I'm on a trial version of RS but I'm not trying it again as the reinstall cycle took me a whole day!

9 comments
Comment actions Permalink

Hello andy,

we didn't try ReSharper under XP 64. However, if VS.NET 2003 works in this
environment,
I don't see why ReSharper shouldn't work. I also don't understand how ReSharper
could
damage VS in such a way that VS runs out of memory - especially, after (as
you said yourself)
ReSharper had been disabled. Could you please provide more detailed information
about the
problem and your actions?


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

When loading VS.net I get a crash from ReSharper, invalid pointer. The
AddIn then disables itself but it has then trashed VS. From then on
when I load a solution or even create an empty one then add a project
the moemory goes through the roof until crashing. I had to reinstall
XP64 to get it working again as simply removing VS and reinstalling
didnt fix it! Anyone else had similar problems? Luckily I'm on a trial
version of RS but I'm not trying it again as the reinstall cycle took
me a whole day!



0
Comment actions Permalink

I am unable to provide further information as I am not willing to install RS again. I have rebuilt the machine and installed VS again and I'm experiencing no problems with memory leaks. All I know is that previously I installed VS then RS and the first time I started VS I got an invalid pointer exception thrown by the RS AddIn, from then on VS was broken. I have repeated the same install process but without installing RS and VS it is giving me no problems. For me to install RS again and potentially break VS would involve a few hours reinstalling windows and my RS evaluation expires in a few days time anyway. I just wondered if anyone else had similar problems. On another note does the RS AddIn work with VS2005, I realise some functionality has been added by Mircosoft that provides that similar to RS?
-Andy

0
Comment actions Permalink

Hello andy,

EAP (Early Access Program) for ReSharper 2.0 that works under VS 2003 and
VS 2005 will start soon.
I agree with you that it would be very interesting for us to know about other
users experience with
ReSharper under XP64.

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

I am unable to provide further information as I am not willing to
install RS again. I have rebuilt the machine and installed VS again
and I'm experiencing no problems with memory leaks. All I know is that
previously I installed VS then RS and the first time I started VS I
got an invalid pointer exception thrown by the RS AddIn, from then on
VS was broken. I have repeated the same install process but without
installing RS and VS it is giving me no problems. For me to install RS
again and potentially break VS would involve a few hours reinstalling
windows and my RS evaluation expires in a few days time anyway. I just
wondered if anyone else had similar problems. On another note does the
RS AddIn work with VS2005, I realise some functionality has been added
by Mircosoft that provides that similar to RS?

-Andy



0
Comment actions Permalink

OK I just had a thought. It may not be perfect but I'll put on VMWare or VirtualPC on the machine, create a virtual machine and install XP64 on it and then VS and RS and see if I get the same problem. I will let you know the outcome.
-Andy

0
Comment actions Permalink

Thank you, Andy.
We'll wait for information from you.

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

OK I just had a thought. It may not be perfect but I'll put on VMWare
or VirtualPC on the machine, create a virtual machine and install XP64
on it and then VS and RS and see if I get the same problem. I will let
you know the outcome.

-Andy



0
Comment actions Permalink

I think you will find that your PInvoke declarations are not portable to 64 bits.

I just ran FxCop 1.32 over the JetBrains dll's and got 20000 issues. Turning off naming and globalization issues got it down to 9000, but there are quite a few issues you should be looking at, including "PInvoke declarations should be portable", "Value type fields should be portable" and lots of problems with Dispose, unused code, concatenating string, etc.

0
Comment actions Permalink

I just checked and Virtual PC wont even run on x64! Also looking at VMWare x64 isn't supported as a host or guest OS!

I will ghost my machine and try it, I guess that is a better way of testing anyway as you rule out the VM being an issue.

Although regarding the last post it seems this is probably a genuine issue with RS. I will give it a try later and capture the error message / debug info.

-Andy

0
Comment actions Permalink

Dmitry,

I should have replied to you about this issue. See my other post.

0
Comment actions Permalink

Hello Philip,

oops, we should have figured out this. Thank you a lot.
This easily explains an invalid pointer error that Andy got on XP 64.
We'll fix PInvoke declarations in 2.0, though you understand that it may take
some time, and we may not have this time before 2.0 EAP (but certainly we
will have it before 2.0 release).

I admit that we're still not running FxCop on ReSharper assemblies. I think
we should reconsider
this, and your message is a good indication of this.

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

I think you will find that your PInvoke declarations are not portable
to 64 bits.

I just ran FxCop 1.32 over the JetBrains dll's and got 20000 issues.
Turning off naming and globalization issues got it down to 9000, but
there are quite a few issues you should be looking at, including
"PInvoke declarations should be portable", "Value type fields should
be portable" and lots of problems with Dispose, unused code,
concatenating string, etc.



0

Please sign in to leave a comment.