Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error
2 Pages12>
Rider freezes UI very often when combined with NCrunch
Options
Previous Topic Next Topic
TimVisma
#1 Posted : Thursday, September 25, 2025 2:35:02 PM(UTC)
Rank: Member

Groups: Registered
Joined: 6/27/2024(UTC)
Posts: 17
Location: Netherlands
Hello everyone,

I've been using NCrunch with Rider for quite some time now (more then a year and I love it). However, I've noticed Rider's UI freezing more and more often, which is becoming quite annoying. My colleagues aren't experiencing this issue. I also disabled NCrunch as a plugin (completely) for a while, and then I had no problems at all, and Rider works flawlessly.

Rider's UI freeze goes away fairly quickly when I click on another application.

I've shared the log files in a contact form because they might contain sensitive data.

Quote:
CPU

Intel(R) Core(TM) Ultra 7 255U

Base speed: 2,00 GHz
Sockets: 1
Cores: 12
Logical processors: 14
Virtualization: Enabled
L1 cache: 1,2 MB
L2 cache: 10,0 MB
L3 cache: 12,0 MB

Utilization 21%
Speed 3,70 GHz
Up time 2:07:17:53
Processes 434
Threads 8262
Handles 225518

32GB RAM

JetBrains Rider 2025.2.2 - Build #RD-252.26199.154, built on September 18, 2025 (same issue on older versions)
Ncrunch: 5.18.0.2


Configuration:
CPU: 7 cores for Rider and 7 for NCrunch
Max processing threads: 1
Engine Optimisation: Optimise for fastest test execution
Parallel: Off
RDI: Off

Hopefully you'll find something that will help me work normally again with Rider in combination with NCrunch ;).

Greetz,

Tim
Back to top
 |  Edit by user
Remco
#2 Posted : Friday, September 26, 2025 12:07:36 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,403

Thanks: 1003 times
Was thanked: 1346 time(s) in 1249 post(s)
Hi Tim,

I've been trying to track down an issue which I suspect may be the same as this one.

Can you share any more detail on the nature of the freezes? How often do you get them, and how long do they show for? Do you sometimes have sessions that don't have them?

Also, can you confirm whether you enabled detailed logging to try and troubleshoot the freezing? I'm wondering if it still happens when Log Verbosity is set to Summary.
Back to top
 |  Edit by user
TimVisma
#3 Posted : Friday, September 26, 2025 9:26:45 AM(UTC)
Rank: Member

Groups: Registered
Joined: 6/27/2024(UTC)
Posts: 17
Location: Netherlands
Hi Remco,

Where can I find the logfiles? I can not find them.

The freezes occur more quickly when I have larger solutions open, but they persist when I close the larger solutions (most don't even have NCrunch enabled). Only after restarting Rider does it initially improve. Unfortunately, I can't find any reason behind it, which is why the IDE freezes much more often.

The freezes are often short-lived, and I can now get back to them sooner by clicking on another program and returning to Rider. However, the CPU immediately reaches 100%.

What else can I do to determine the error/cause?

I've been enabling the 'Log to output window' setting for a while now to try and diagnose the problem, but where can I find this log?

Greetz, Tim
Back to top
Remco
#4 Posted : Friday, September 26, 2025 9:33:08 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,403

Thanks: 1003 times
Was thanked: 1346 time(s) in 1249 post(s)
Hi Tim,

The 'Log to output window' setting doesn't work under Rider, as it doesn't have an output window like VS does for reporting log details.

When logging is enabled under Rider, the logs are written into the backend Rider logs. I noticed in the data you sent through that you have a lot of data landing in these logs, and I'm not sure how efficiently the Rider backend can process this. It may be implicated in the freezes. I think it's best if we first try to rule it out.

Could you try setting your Log Verbosity to Summary and see if this has any affect on the freezes?
Back to top
TimVisma
#5 Posted : Friday, September 26, 2025 10:23:05 AM(UTC)
Rank: Member

Groups: Registered
Joined: 6/27/2024(UTC)
Posts: 17
Location: Netherlands
I've enabled Log Verbosity to Summary.

Which Rider log files could I view myself that are relevant? For example, Backend or threadDumps-freezes?
Back to top
Remco
#6 Posted : Friday, September 26, 2025 10:25:44 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,403

Thanks: 1003 times
Was thanked: 1346 time(s) in 1249 post(s)
TimVisma;18344 wrote:

Which Rider log files could I view myself that are relevant? For example, Backend or threadDumps-freezes?


At this stage, I'm not sure. It depends on whether the freeze is related to the vast amount of data being logged. If you can confirm whether changing the log verbosity has an effect, this will narrow the issue down somewhat.
Back to top
Der-Albert.com
#7 Posted : Friday, September 26, 2025 1:41:01 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 5/17/2011(UTC)
Posts: 235

Thanks: 14 times
Was thanked: 57 time(s) in 53 post(s)
I can confirm that i also have freezes in Rider, NCrunch seems also be involved.

I had this extremly when the NCrunch Test Tool Window was just at the bottom the Window Window (Just the NCrunch Title or lesse was visible). Had to get the Windows Visible to have Rider stable again.

Will send logs when it happens again.
Back to top
BLOG
Remco
#8 Posted : Friday, September 26, 2025 9:32:16 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,403

Thanks: 1003 times
Was thanked: 1346 time(s) in 1249 post(s)
Thanks for these extra details. I was wondering if I was the only one seeing this issue and that perhaps it was specific to my environment. I now know that is not the case.

There's a few things I've discovered about this problem in my efforts so far to resolve it:
- It's intermittent, and seems to happen regardless of the state of the NCrunch engine. Just by having NCrunch installed, it can happen
- It's originating from the Rider backend process. The problem appears when the main thread in Rider is waiting on the backend for something which seems to take a long time to appear
- There are no NCrunch stack traces directly implicated in the problem. When a debugger is attached to the backend process during a hang, there are no NCrunch threads that seem to be involved
- I seem to get sessions where the problem appears extremely often, enough to be infuriating. Then I get sessions where it never shows up at all. I have found it very hard to reproduce at will
- I suspected this might be caused by heap compactions but initial profiling results suggest they are not involved
- I haven't found log files to be any help here. Whatever is going wrong, the logs don't show it (neither NCrunch nor Rider)
- I really hate this problem

It's likely this needs to be solved deductively. Any patterns you can find to help narrow it down will really help me a lot.
Back to top
TimVisma
#9 Posted : Monday, September 29, 2025 9:05:40 AM(UTC)
Rank: Member

Groups: Registered
Joined: 6/27/2024(UTC)
Posts: 17
Location: Netherlands
Hello,

I have test it with log verbosity with summary, but unfortunately no difference.

Is it possible that NCrunch sometimes has issues with GitHub Copilot? (Other colleagues have this combination as well, but no problem.)

I also tried temporarily disabling copilot, but no difference.
idea log with error Github Copilot
Back to top
 |  Edit by user
Remco
#10 Posted : Monday, September 29, 2025 9:14:56 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,403

Thanks: 1003 times
Was thanked: 1346 time(s) in 1249 post(s)
TimVisma;18349 wrote:

I have test it with log verbosity with summary, but unfortunately no difference.


Thanks for confirming this.

TimVisma;18349 wrote:

Is it possible that NCrunch sometimes has issues with GitHub Copilot? (Other colleagues have this combination as well, but no problem.)


No, or at least, I don't think this specific problem is being caused by Copilot. I have seen it before without Copilot being loaded.

Can you tell me more about the setup your colleagues are running? Are they also using Rider? If so, are there any notable configuration differences between your machine and theirs?
Back to top
Der-Albert.com
#13 Posted : Wednesday, October 1, 2025 8:33:43 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 5/17/2011(UTC)
Posts: 235

Thanks: 14 times
Was thanked: 57 time(s) in 53 post(s)
Back to top
BLOG
TimVisma
#11 Posted : Friday, October 10, 2025 10:26:18 AM(UTC)
Rank: Member

Groups: Registered
Joined: 6/27/2024(UTC)
Posts: 17
Location: Netherlands
Remco;18350 wrote:
TimVisma;18349 wrote:

I have test it with log verbosity with summary, but unfortunately no difference.


Thanks for confirming this.

TimVisma;18349 wrote:

Is it possible that NCrunch sometimes has issues with GitHub Copilot? (Other colleagues have this combination as well, but no problem.)


No, or at least, I don't think this specific problem is being caused by Copilot. I have seen it before without Copilot being loaded.

Can you tell me more about the setup your colleagues are running? Are they also using Rider? If so, are there any notable configuration differences between your machine and theirs?


My colleagues are running also with Rider. As far as I know they don't have any other crazy configurations, but I'll meet again next week to discuss this.

By the way, it is often more annoying when I have multiple solutions open to work on.
Back to top
 |  Edit by user
Remco
#12 Posted : Friday, October 10, 2025 12:17:37 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,403

Thanks: 1003 times
Was thanked: 1346 time(s) in 1249 post(s)
TimVisma;18387 wrote:

My colleagues are running also with Rider. As far as I know they don't have any other crazy configurations, but I'll meet again next week to discuss this.

By the way, it is often more annoying when I have multiple solutions open to work on.


Thanks. I'm continuing to try and pin this down. Any information you can provide at all will be helpful.
Back to top
Der-Albert.com
#14 Posted : Wednesday, October 15, 2025 7:15:19 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 5/17/2011(UTC)
Posts: 235

Thanks: 14 times
Was thanked: 57 time(s) in 53 post(s)
Yeah, had a total Rider Freeze (had to kill it) a couple minutes ago (Two Times)

Worked two days (after Vacation) without any noticeable problems. But then I did it again

Reproduceable way, everything with the mouse.

* Open the NCrunch Tests Windows (Docked Pinned in Rider, Bottom Left in my Case).
* Resize the tool window (I may case dragging the top border down) to the smallest size possible (only the title visible) to have more visible lines in the Editor
* Open a different Tool Window in the same Area (in my case the Rider Unit Test Window)
* Open the NCrunch Tests Window again
* Freeze
Back to top
BLOG
 |  Edit by user
Remco
#15 Posted : Wednesday, October 15, 2025 7:28:42 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,403

Thanks: 1003 times
Was thanked: 1346 time(s) in 1249 post(s)
Thanks for sharing this. Do you have more than one monitor, and differing DPI settings between them?

It looks a lot like this issue rather than the random freezes (I am certain they are both very real and different issues)
Back to top
Der-Albert.com
#16 Posted : Wednesday, October 15, 2025 7:35:50 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 5/17/2011(UTC)
Posts: 235

Thanks: 14 times
Was thanked: 57 time(s) in 53 post(s)
Currently (at Work)

Two 32" 4K Monitors, Both scaling 125%. Both horizontal.

Rider on the Main Monitor (On the right side)

The other one is VS not Rider, so i wrote it here, and adding details ;)

Rider 2025.2.3 and NCrunch 5.18.0.2 (manually installed after NCrunch nagged me about the new Version, because it's not available in the JetBrains Marketplace)
Back to top
BLOG
 |  Edit by user
Remco
#17 Posted : Wednesday, October 15, 2025 8:02:40 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,403

Thanks: 1003 times
Was thanked: 1346 time(s) in 1249 post(s)
Can you confirm whether you're able to crash this every time using the steps to reproduce you've described? (As per my usual luck, I can't get it to happen).

The thread referenced above contains an NCrunch build that restructures how the rendering in the Tests Window trace output works, mitigating issues related to massive CPU consumption when the trace output area gets too small. If you can still reproduce the issue now, I'd be interested to know if this build solves it. If not, I'm probably going to need to ask if you're able to get me a stack trace of the main thread by hooking a debugger onto the NCrunch engine process when the crash happens.

Also, sorry about the version nags. These should go away when the next release goes out (won't be long now).
Back to top
TimVisma
#19 Posted : Wednesday, October 15, 2025 8:59:44 AM(UTC)
Rank: Member

Groups: Registered
Joined: 6/27/2024(UTC)
Posts: 17
Location: Netherlands
I also submitted a ticket to Rider themselves, and they responded. Perhaps this can help you?

https://youtrack.jetbrains.com/issue/RIDER-130798
Back to top
TimVisma
#21 Posted : Wednesday, October 15, 2025 9:51:42 AM(UTC)
Rank: Member

Groups: Registered
Joined: 6/27/2024(UTC)
Posts: 17
Location: Netherlands
I got today a IDE Internal Errors:

Quote:

Freeze in EDT for 14 seconds
Sampled time: 1900ms, sampling rate: 100ms, GC time: 255ms (3%), Class loading: 0%, CPU load: 3%

com.intellij.diagnostic.Freeze
at com.sun.jna.Native.invokeInt(Native Method)
at com.sun.jna.Function.invoke(Function.java:429)
at com.sun.jna.Function.invoke(Function.java:364)
at com.sun.jna.Library$Handler.invoke(Library.java:270)
at jdk.proxy2/jdk.proxy2.$Proxy117.MoveWindow(Unknown Source)
at com.jetbrains.wormhole.interop.windows.WindowsNativeWindowProxy.move(WindowsNativeWindowProxy.kt:99)
at com.jetbrains.wormhole.interop.windows.WindowsNativeWindowProxy.arrange(WindowsNativeWindowProxy.kt:46)
at com.jetbrains.wormhole.awt.states.FinalState.arrange(FinalState.kt:85)
at com.jetbrains.wormhole.awt.Wormhole.z(Wormhole.kt:139)
at com.jetbrains.wormhole.awt.Wormhole.reshape(Wormhole.kt:97)
at java.desktop/java.awt.Component.setBounds(Component.java:2371)
at com.remco.software.ncrunch.toolwindows.BaseToolWindowFactory$WormholeWindow.setWormholeSize(BaseToolWindowFactory.kt:204)
at com.remco.software.ncrunch.toolwindows.BaseToolWindowFactory$WormholeWindow._init_$lambda$2(BaseToolWindowFactory.kt:118)
at com.remco.software.ncrunch.toolwindows.BaseToolWindowFactory$WormholeWindow$$Lambda/0x000002efa32ee278.invoke(Unknown Source)
at com.remco.software.ncrunch.ComponentScalingMonitor.applyNewScaling(ComponentScalingMonitor.kt:89)
at com.remco.software.ncrunch.ComponentScalingMonitor.doCheck(ComponentScalingMonitor.kt:67)
at com.remco.software.ncrunch.ComponentScalingMonitor.checkMonitorTimer$lambda$1(ComponentScalingMonitor.kt:30)
at com.remco.software.ncrunch.ComponentScalingMonitor$$Lambda/0x000002efa32ee020.actionPerformed(Unknown Source)
at java.desktop/javax.swing.Timer.fireActionPerformed(Timer.java:311)
at java.desktop/javax.swing.Timer$DoPostEvent.run(Timer.java:243)
at com.intellij.util.concurrency.ChildContext$runInChildContext$1.invoke(propagation.kt:167)
at com.intellij.util.concurrency.ChildContext$runInChildContext$1.invoke(propagation.kt:167)
at com.intellij.util.concurrency.ChildContext.runInChildContext(propagation.kt:173)
at com.intellij.util.concurrency.ChildContext.runInChildContext(propagation.kt:167)
at com.intellij.util.concurrency.ContextRunnable.run(ContextRunnable.java:27)
at java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:318)
at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:781)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:728)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:722)
at java.base@21.0.8/java.security.AccessController.executePrivileged(AccessController.java:778)
at java.base@21.0.8/java.security.AccessController.doPrivileged(AccessController.java:400)
at java.base@21.0.8/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:87)
at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:750)
at com.intellij.ide.IdeEventQueue.defaultDispatchEvent(IdeEventQueue.kt:595)
at com.intellij.ide.IdeEventQueue._dispatchEvent(IdeEventQueue.kt:488)
at com.intellij.ide.IdeEventQueue.dispatchEvent$lambda$12$lambda$11$lambda$10$lambda$9(IdeEventQueue.kt:313)
at com.intellij.ide.IdeEventQueue$$Lambda/0x000002efa291bc48.compute(Unknown Source)
at com.intellij.openapi.progress.impl.CoreProgressManager.computePrioritized(CoreProgressManager.java:865)
at com.intellij.ide.IdeEventQueue.dispatchEvent$lambda$12$lambda$11$lambda$10(IdeEventQueue.kt:312)
at com.intellij.ide.IdeEventQueue$$Lambda/0x000002efa277d878.invoke(Unknown Source)
at com.intellij.ide.IdeEventQueueKt.performActivity$lambda$3(IdeEventQueue.kt:974)
at com.intellij.ide.IdeEventQueueKt$$Lambda/0x000002efa277e388.run(Unknown Source)
at com.intellij.openapi.application.TransactionGuardImpl.performActivity(TransactionGuardImpl.java:110)
at com.intellij.ide.IdeEventQueueKt.performActivity(IdeEventQueue.kt:974)
at com.intellij.ide.IdeEventQueue.dispatchEvent$lambda$12(IdeEventQueue.kt:307)
at com.intellij.ide.IdeEventQueue$$Lambda/0x000002efa27769d0.run(Unknown Source)
at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.kt:347)
at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:207)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:128)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:117)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:113)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:105)
at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:92)



Quote:

java.awt.EventDispatchThread.run 1900ms
java.awt.EventDispatchThread.pumpEvents 1900ms
java.awt.EventDispatchThread.pumpEvents 1900ms
java.awt.EventDispatchThread.pumpEventsForHierarchy 1900ms
java.awt.EventDispatchThread.pumpEventsForFilter 1900ms
java.awt.EventDispatchThread.pumpOneEventForFilters 1900ms
com.intellij.ide.IdeEventQueue.dispatchEvent 1900ms
com.intellij.ide.IdeEventQueue$$Lambda/0x000002efa27769d0.run 1900ms
com.intellij.ide.IdeEventQueue.dispatchEvent$lambda$12 1900ms
com.intellij.ide.IdeEventQueueKt.performActivity 1900ms
com.intellij.openapi.application.TransactionGuardImpl.performActivity 1900ms
com.intellij.ide.IdeEventQueueKt$$Lambda/0x000002efa277e388.run 1900ms
com.intellij.ide.IdeEventQueueKt.performActivity$lambda$3 1900ms
com.intellij.ide.IdeEventQueue$$Lambda/0x000002efa277d878.invoke 1900ms
com.intellij.ide.IdeEventQueue.dispatchEvent$lambda$12$lambda$11$lambda$10 1900ms
com.intellij.openapi.progress.impl.CoreProgressManager.computePrioritized 1900ms
com.intellij.ide.IdeEventQueue$$Lambda/0x000002efa291bc48.compute 1900ms
com.intellij.ide.IdeEventQueue.dispatchEvent$lambda$12$lambda$11$lambda$10$lambda$9 1900ms
com.intellij.ide.IdeEventQueue._dispatchEvent 1900ms
com.intellij.ide.IdeEventQueue.defaultDispatchEvent 1900ms
java.awt.EventQueue.dispatchEvent 1900ms
java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege 1900ms
java.security.AccessController.doPrivileged 1900ms
java.security.AccessController.executePrivileged 1900ms
java.awt.EventQueue$4.run 1900ms
java.awt.EventQueue$4.run 1900ms
java.awt.EventQueue.dispatchEventImpl 1900ms
java.awt.event.InvocationEvent.dispatch 1900ms
com.intellij.util.concurrency.ContextRunnable.run 1900ms
com.intellij.util.concurrency.ChildContext.runInChildContext 1900ms
com.intellij.util.concurrency.ChildContext.runInChildContext 1900ms
com.intellij.util.concurrency.ChildContext$runInChildContext$1.invoke 1900ms
com.intellij.util.concurrency.ChildContext$runInChildContext$1.invoke 1900ms
javax.swing.Timer$DoPostEvent.run 1900ms
javax.swing.Timer.fireActionPerformed 1900ms
com.remco.software.ncrunch.ComponentScalingMonitor$$Lambda/0x000002efa32ee020.actionPerformed 1900ms
com.remco.software.ncrunch.ComponentScalingMonitor.checkMonitorTimer$lambda$1 1900ms
com.remco.software.ncrunch.ComponentScalingMonitor.doCheck 1900ms
com.remco.software.ncrunch.ComponentScalingMonitor.applyNewScaling 1900ms
com.remco.software.ncrunch.toolwindows.BaseToolWindowFactory$WormholeWindow$$Lambda/0x000002efa32ee278.invoke 1900ms
com.remco.software.ncrunch.toolwindows.BaseToolWindowFactory$WormholeWindow._init_$lambda$2 1900ms
com.remco.software.ncrunch.toolwindows.BaseToolWindowFactory$WormholeWindow.setWormholeSize 1900ms
java.awt.Component.setBounds 1900ms
com.jetbrains.wormhole.awt.Wormhole.reshape 1900ms
com.jetbrains.wormhole.awt.Wormhole.z 1900ms
com.jetbrains.wormhole.awt.states.FinalState.arrange 1900ms
com.jetbrains.wormhole.interop.windows.WindowsNativeWindowProxy.arrange 1900ms
com.jetbrains.wormhole.interop.windows.WindowsNativeWindowProxy.move 1900ms
jdk.proxy2.$Proxy117.MoveWindow 1900ms
com.sun.jna.Library$Handler.invoke 1900ms
com.sun.jna.Function.invoke 1900ms
com.sun.jna.Function.invoke 1900ms
com.sun.jna.Native.invokeInt 1900ms
Back to top
Der-Albert.com
#18 Posted : Wednesday, October 15, 2025 10:43:08 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 5/17/2011(UTC)
Posts: 235

Thanks: 14 times
Was thanked: 57 time(s) in 53 post(s)
Remco;18399 wrote:
Can you confirm whether you're able to crash this every time using the steps to reproduce you've described? (As per my usual luck, I can't get it to happen).

The thread referenced above contains an NCrunch build that restructures how the rendering in the Tests Window trace output works, mitigating issues related to massive CPU consumption when the trace output area gets too small. If you can still reproduce the issue now, I'd be interested to know if this build solves it. If not, I'm probably going to need to ask if you're able to get me a stack trace of the main thread by hooking a debugger onto the NCrunch engine process when the crash happens.

Also, sorry about the version nags. These should go away when the next release goes out (won't be long now).


Reproducable freeze with:
5.18.0.2
5.17.0.1
5.16.0.5

I just Open Rider with the Solution.
I wait for NCrunch Tests Window saying "No test are queueed for execution".
I resize the Tool Window Area, as small as possible.
I switch the Tool Window and back to NCrunch Tests
Rider freezed
I'm pissed an kill Rider ;/

Uninstalled NCrunch.
Tested this with a different Tool Window (NuGet, which has some "Action") in the Docking Area.
No freeze.

So, i need some advice how to attach the Debugger to NCrunch without Rider.
Back to top
BLOG
Users browsing this topic
Guest (2)
2 Pages12>
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.158 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download