Daily Usage Issues

Rider plugin exception "Must be executed on UI thread or background threads with special permission"

Started by cheil on 1,824 views

I recently installed the Rider plugin (v5.3.0.2) on Rider 2023.3.4 and saw the error below twice this afternoon. I am on Windows 10 as well.

I did experiment with moving the NCrunch window around the IDE, floating, docked/undocked, etc. which might have triggered it given the description of the error message.


Must be executed on UI thread or background threads with special permissions

java.lang.IllegalStateException: |E| Wrong thread RdSignal: `RiderDebugRunner.DebuggerWorkerModel.detachTarget`
	at com.jetbrains.rdclient.protocol.RdDispatcher.assertThread(RdDispatcher.kt:69)
	at com.jetbrains.rd.framework.base.RdReactiveBase.assertThreading(RdReactiveBase.kt:28)
	at com.jetbrains.rd.framework.impl.RdSignal.fire(RdSignal.kt:45)
	at com.jetbrains.rd.util.reactive.InterfacesKt.fire(Interfaces.kt:163)
	at com.jetbrains.rider.debugger.DebuggerWorkerProcessHandlerBase.detachProcessImpl(DebuggerWorkerProcessHandlerBase.kt:41)
	at com.jetbrains.rider.debugger.DebuggerWorkerProcessHandler.detachProcessImpl(DebuggerWorkerProcessHandler.kt:148)
	at com.intellij.execution.process.ProcessHandler.lambda$detachProcess$1(ProcessHandler.java:140)
	at com.intellij.execution.process.ProcessHandler$TasksRunner.execute(ProcessHandler.java:322)
	at com.intellij.execution.process.ProcessHandler.detachProcess(ProcessHandler.java:137)
	at com.remco.software.ncrunch.editor.EditorIntegrationService$detachFromProcess$1$1.invoke(EditorIntegrationService.kt:106)
	at com.remco.software.ncrunch.editor.EditorIntegrationService$detachFromProcess$1$1.invoke(EditorIntegrationService.kt:104)
	at com.remco.software.ncrunch.ErrorService$Companion.doWithErrorHandling(ErrorService.kt:44)
	at com.remco.software.ncrunch.editor.EditorIntegrationService$detachFromProcess$1.invokeSuspend(EditorIntegrationService.kt:104)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:108)
	at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:115)
	at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:103)
	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:584)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:793)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:697)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:684)

Hi, thanks for taking the time to give such a detailed error report. I had already fixed the problem and it will be in our next build. But the extra information you gave about undocking the windows made clear to me why it was happening!

Thanks!
No problem, thank you!

Post a reply

Log in to reply.