shekharpro / mb-unit

Automatically exported from code.google.com/p/mb-unit
0 stars 0 forks source link

Refreshing the R# 4.1 Test Explorer causes "Attempted to read or write protected memory. This is often an indication that other memory is corrupt" #338

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Open my VS2008 solution (sorry; I cannot provide it, but I can allow you
VNC access if required...?)
2. Open the Test Explorer (or, later, refresh it)
3. Observe exception

What is the expected output? What do you see instead?
I expect to see the test-explorer and all of the (xunit) tests it has
found.  Instead, I see the exception, and the test-explorer is only
partially populated once I submit/ignore it from R#'s dialogue

What version of the product are you using? On what operating system?
R# 4.1 release + Gallio 3.0.4.485 on Windows 2008 Server Enterprise x64

Please provide any additional information below.
This also (or at least, something similar) happens reasonably often when I
run unit-tests from the unit-test session panel.

I don't really know whether this is a bug in R# or Gallio; I am including
it here since Gallio is mentioned in the stack trace.

The JetBrains issue is http://www.jetbrains.net/jira/browse/RSRP-85930

Original issue reported on code.google.com by peter.mo...@gmail.com on 14 Nov 2008 at 8:54

GoogleCodeExporter commented 8 years ago
This does not happen on my home computer, against the same solution.

My home computer is running VS2008 inside of a Win2k8 x64 VMWare virtual 
machine; essentially the same 
setup (Windows-wise) as at work, except of course virtualised.

As mentioned; welcome to VNC access if required, at work; I'm in the GMT 
timezone (London).

Original comment by peter.mo...@gmail.com on 15 Nov 2008 at 5:50

GoogleCodeExporter commented 8 years ago
Actually, this has just happened on my home computer too; it happened when I 
double-clicked a test in the 
unit-test session panel in R#.

Original comment by peter.mo...@gmail.com on 15 Nov 2008 at 7:02

GoogleCodeExporter commented 8 years ago
I just noticed that at home, I have r481 installed, not r485 as at work.  How 
can I tell which version R# is using to 
run and explore the tests?  I store gallio in source control, but I guess VS 
still needs it to be formally installed to 
be able to know about the R# plugin - unless there is a similar utility to 
xunit.net's xunit.installer.exe which is a 
windows form with 3 buttons, one each to install/uninstall integration for 
TestDriven, R#, and something else?

Original comment by peter.mo...@gmail.com on 16 Nov 2008 at 11:21

GoogleCodeExporter commented 8 years ago
There is no similar utility because we actually install a lot of different bits 
and
pieces (such as documentation, plugins for VSTS and R#, etc.) and it makes more 
sense
to just use the MSI installer.

The version used to run the tests from R# will be whatever you installed, not 
what
was in the source tree (unfortunately).

Several people have reported this error but it's proving hard to find.  If you 
have
some time to help narrow it down, I'd love to have a reproducible case so that 
we can
either find a bug in Gallio or if it's a R# problem at then we can give 
JetBrains a
good idea of where to start looking.

So far I've had no luck reproducing this problem myself.

Original comment by jeff.br...@gmail.com on 20 Nov 2008 at 12:57

GoogleCodeExporter commented 8 years ago
Since installing 3.0.5, I don't remember seeing this.  If I see it again, I'll 
post
here to invite you to screen-share and debug, if you like.  Which timezone are 
you in?

Original comment by peter.mo...@gmail.com on 27 Nov 2008 at 1:22

GoogleCodeExporter commented 8 years ago
I'm in Pacific Standard Time.  :-)

I'm going to close this issue for now but let's reopen it if you see bad 
behavior again.

Original comment by jeff.br...@gmail.com on 19 Feb 2009 at 5:07