UnitTestRunner locks up.

Hi I'm experiencing Resharper 2.0 locking up to a point where i have to kill
the devenv process when i run tests that use NUnitASP.
Another test project in the same solution that just tests the Business Layer
(NUnitASP dll less) does not lock up.

-John


4 comments
Comment actions Permalink

Debugging this problem further, I created a sample project with a simple
testfixture using nunitasp. While the lock up does not seem to occur at
first after I switch tabs in the unittest runner gui (All, Failed, Ignored,
then back to all) it locks up.
Process Explorer shows the devenv process taking 50%~ of the CPU (its got
HyperThreading enabled) but visual studio does not respond.
I'm using vs2003.

This is what ProcessExplorer shows as the stack for the locked thread.

ntoskrnl.exe!ExReleaseResourceLite+0x2b4
ntoskrnl.exe!IoPageRead+0x892
hal.dll+0x2ef2
system.windows.forms.dll+0x128c9
system.windows.forms.dll+0x12845
USER32.dll!GetDC+0x14f
USER32.dll!DefWindowProcW+0x184
USER32.dll!DefWindowProcW+0x1d0
ntdll.dll!KiUserCallbackDispatcher+0x13
USER32.dll!DispatchMessageA+0xf
msenv.dll+0x19a59
ole32.dll!ReadFmtUserTypeStg+0x4d6
ole32.dll!ReadFmtUserTypeStg+0x48c
ole32.dll!CoImpersonateClient+0x104
ole32.dll!CoWaitForMultipleHandles+0xe6
mscorwks.dll!GetCompileInfo+0x5a8da
mscorwks.dll!GetCompileInfo+0x5a865
mscorwks.dll!GetCompileInfo+0x598c8
mscorwks.dll!GetCompileInfo+0x4d5c5
mscorwks.dll!GetCompileInfo+0x4d1ee
mscorwks.dll!GetCompileInfo+0x4d124
mscorwks.dll!GetCompileInfo+0x55cc2
mscorwks.dll!ReleaseFusionInterfaces+0x67ee5
mscorwks.dll!GetCompileInfo+0x1d38b
mscorwks.dll!CorExitProcess+0x1c694


-John

"John Morales" <jmorales@gmail.com> wrote in message
news:e4fj7f$oan$1@is.intellij.net...

Hi I'm experiencing Resharper 2.0 locking up to a point where i have to
kill the devenv process when i run tests that use NUnitASP.
Another test project in the same solution that just tests the Business
Layer (NUnitASP dll less) does not lock up.

>

-John



0
Comment actions Permalink

Looks like the lockup has nothing to due with NUnitASP. Removing the
reference from the sample project still repros the same problem. Attached is
the sample project.

"John Morales" <jmorales@gmail.com> wrote in message
news:e4fl7j$278$1@is.intellij.net...

Debugging this problem further, I created a sample project with a simple
testfixture using nunitasp. While the lock up does not seem to occur at
first after I switch tabs in the unittest runner gui (All, Failed,
Ignored,
then back to all) it locks up.
Process Explorer shows the devenv process taking 50%~ of the CPU (its got
HyperThreading enabled) but visual studio does not respond.
I'm using vs2003.

>

This is what ProcessExplorer shows as the stack for the locked thread.

>

ntoskrnl.exe!ExReleaseResourceLite+0x2b4
ntoskrnl.exe!IoPageRead+0x892
hal.dll+0x2ef2
system.windows.forms.dll+0x128c9
system.windows.forms.dll+0x12845
USER32.dll!GetDC+0x14f
USER32.dll!DefWindowProcW+0x184
USER32.dll!DefWindowProcW+0x1d0
ntdll.dll!KiUserCallbackDispatcher+0x13
USER32.dll!DispatchMessageA+0xf
msenv.dll+0x19a59
ole32.dll!ReadFmtUserTypeStg+0x4d6
ole32.dll!ReadFmtUserTypeStg+0x48c
ole32.dll!CoImpersonateClient+0x104
ole32.dll!CoWaitForMultipleHandles+0xe6
mscorwks.dll!GetCompileInfo+0x5a8da
mscorwks.dll!GetCompileInfo+0x5a865
mscorwks.dll!GetCompileInfo+0x598c8
mscorwks.dll!GetCompileInfo+0x4d5c5
mscorwks.dll!GetCompileInfo+0x4d1ee
mscorwks.dll!GetCompileInfo+0x4d124
mscorwks.dll!GetCompileInfo+0x55cc2
mscorwks.dll!ReleaseFusionInterfaces+0x67ee5
mscorwks.dll!GetCompileInfo+0x1d38b
mscorwks.dll!CorExitProcess+0x1c694

>
>

-John

>

"John Morales" <jmorales@gmail.com> wrote in message
news:e4fj7f$oan$1@is.intellij.net...

>> Hi I'm experiencing Resharper 2.0 locking up to a point where i have to
>> kill the devenv process when i run tests that use NUnitASP.
>> Another test project in the same solution that just tests the Business
>> Layer (NUnitASP dll less) does not lock up.
>>
>> -John
>>
>





0
Comment actions Permalink

Hello John,

For a workaround try "Show Desktop" or ]]> D - that seems to clear
the lock-up for me.

Ronnie

Looks like the lockup has nothing to due with NUnitASP. Removing the
reference from the sample project still repros the same problem.
Attached is the sample project.

"John Morales" <jmorales@gmail.com> wrote in message
news:e4fl7j$278$1@is.intellij.net...

>> Debugging this problem further, I created a sample project with a
>> simple
>> testfixture using nunitasp. While the lock up does not seem to occur
>> at
>> first after I switch tabs in the unittest runner gui (All, Failed,
>> Ignored,
>> then back to all) it locks up.
>> Process Explorer shows the devenv process taking 50%~ of the CPU (its
>> got
>> HyperThreading enabled) but visual studio does not respond.
>> I'm using vs2003.
>> This is what ProcessExplorer shows as the stack for the locked
>> thread.
>>
>> ntoskrnl.exe!ExReleaseResourceLite+0x2b4
>> ntoskrnl.exe!IoPageRead+0x892
>> hal.dll+0x2ef2
>> system.windows.forms.dll+0x128c9
>> system.windows.forms.dll+0x12845
>> USER32.dll!GetDC+0x14f
>> USER32.dll!DefWindowProcW+0x184
>> USER32.dll!DefWindowProcW+0x1d0
>> ntdll.dll!KiUserCallbackDispatcher+0x13
>> USER32.dll!DispatchMessageA+0xf
>> msenv.dll+0x19a59
>> ole32.dll!ReadFmtUserTypeStg+0x4d6
>> ole32.dll!ReadFmtUserTypeStg+0x48c
>> ole32.dll!CoImpersonateClient+0x104
>> ole32.dll!CoWaitForMultipleHandles+0xe6
>> mscorwks.dll!GetCompileInfo+0x5a8da
>> mscorwks.dll!GetCompileInfo+0x5a865
>> mscorwks.dll!GetCompileInfo+0x598c8
>> mscorwks.dll!GetCompileInfo+0x4d5c5
>> mscorwks.dll!GetCompileInfo+0x4d1ee
>> mscorwks.dll!GetCompileInfo+0x4d124
>> mscorwks.dll!GetCompileInfo+0x55cc2
>> mscorwks.dll!ReleaseFusionInterfaces+0x67ee5
>> mscorwks.dll!GetCompileInfo+0x1d38b
>> mscorwks.dll!CorExitProcess+0x1c694
>> -John
>>
>> "John Morales" <jmorales@gmail.com> wrote in message
>> news:e4fj7f$oan$1@is.intellij.net...
>>
>>> Hi I'm experiencing Resharper 2.0 locking up to a point where i have
>>> to
>>> kill the devenv process when i run tests that use NUnitASP.
>>> Another test project in the same solution that just tests the
>>> Business
>>> Layer (NUnitASP dll less) does not lock up.
>>> -John
>>>


0
Comment actions Permalink

Thnak you for the test project.
I'll check it ASAP

--
Eugene Pasynkov
Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"John Morales" <jmorales@gmail.com> wrote in message
news:e4flmp$4fe$1@is.intellij.net...

Looks like the lockup has nothing to due with NUnitASP. Removing the
reference from the sample project still repros the same problem. Attached
is the sample project.

>

"John Morales" <jmorales@gmail.com> wrote in message
news:e4fl7j$278$1@is.intellij.net...

>> Debugging this problem further, I created a sample project with a simple
>> testfixture using nunitasp. While the lock up does not seem to occur at
>> first after I switch tabs in the unittest runner gui (All, Failed,
>> Ignored,
>> then back to all) it locks up.
>> Process Explorer shows the devenv process taking 50%~ of the CPU (its got
>> HyperThreading enabled) but visual studio does not respond.
>> I'm using vs2003.
>>
>> This is what ProcessExplorer shows as the stack for the locked thread.
>>
>> ntoskrnl.exe!ExReleaseResourceLite+0x2b4
>> ntoskrnl.exe!IoPageRead+0x892
>> hal.dll+0x2ef2
>> system.windows.forms.dll+0x128c9
>> system.windows.forms.dll+0x12845
>> USER32.dll!GetDC+0x14f
>> USER32.dll!DefWindowProcW+0x184
>> USER32.dll!DefWindowProcW+0x1d0
>> ntdll.dll!KiUserCallbackDispatcher+0x13
>> USER32.dll!DispatchMessageA+0xf
>> msenv.dll+0x19a59
>> ole32.dll!ReadFmtUserTypeStg+0x4d6
>> ole32.dll!ReadFmtUserTypeStg+0x48c
>> ole32.dll!CoImpersonateClient+0x104
>> ole32.dll!CoWaitForMultipleHandles+0xe6
>> mscorwks.dll!GetCompileInfo+0x5a8da
>> mscorwks.dll!GetCompileInfo+0x5a865
>> mscorwks.dll!GetCompileInfo+0x598c8
>> mscorwks.dll!GetCompileInfo+0x4d5c5
>> mscorwks.dll!GetCompileInfo+0x4d1ee
>> mscorwks.dll!GetCompileInfo+0x4d124
>> mscorwks.dll!GetCompileInfo+0x55cc2
>> mscorwks.dll!ReleaseFusionInterfaces+0x67ee5
>> mscorwks.dll!GetCompileInfo+0x1d38b
>> mscorwks.dll!CorExitProcess+0x1c694
>>
>>
>> -John
>>
>> "John Morales" <jmorales@gmail.com> wrote in message
>> news:e4fj7f$oan$1@is.intellij.net...
>>> Hi I'm experiencing Resharper 2.0 locking up to a point where i have to
>>> kill the devenv process when i run tests that use NUnitASP.
>>> Another test project in the same solution that just tests the Business
>>> Layer (NUnitASP dll less) does not lock up.
>>>
>>> -John
>>>
>>
>>
>
>



0

Please sign in to leave a comment.