I’m not sure how makes the Plastic Plugin I’m guessing it’s Unity and not JetBrains now?
If it’s a JetBrains issue then I can move the issue over to their forums.
I’m constantly having Rider slow right down and become unusable. It happens consistently when adding/removing a new class, but it also happens randomly without those actions.
It’s the same error each time, relating to annotations,
It happens on Windows and Mac.
My temporary workaround is I need to put focus back on Unity so it can recompile, then come back to Rider and it can become usable again. Sometimes I have to do that a few times for it to kick back into action.
It’s extremely annoying and the worst part of Rider/Plastic. However, I love both tools so much that I still grind through them. Would be such an amazing improvement if this could be fixed.
It only happens when the plugin is enabled yeah.
Its pretty consistent and reliable. I wonder if its related to Rider forcing the compile on Unity or something.
I had to turn it off in the end, it was getting too disruptive.
Does it only happen when you have enabled the Version Control package? Or when you have enabled the Rider package? I would like to understand what is the specific package generating the problem.
I’ve had a video call and shown the issue as well. There is a video link in the ticket.
It only happens when the plugin for Rider is enabled yes.
It seems to me that there is a conflict between Unity and Rider plastic plugins. A timing issue.
For example: when I create a script both Unity and Rider are fighting for the same resources.
I think a simple, possibly naive, fix would be adding some kind of wait on Riders’ end. So if Unity is busy, rider should wait in the background (as not to kill performance) until it’s done then do whatever it needs to do.
Thanks for the update and the details. I can see my coworker is already handling the ticket so let’s continue the conversation there to avoid duplicating the threads.
The link above https://support.unity.com/hc/en-us/requests/1557902 does not exist. With unity 6 lts and rider 2024.3.5 I receive the following error in rider:
java.lang.NoSuchMethodError: ‘java.lang.String com.intellij.util.SystemProperties.getLineSeparator()’
at com.codicesoftware.intellij.actions.utils.ActionUtils.bytesToString(ActionUtils.java:247)
at com.codicesoftware.intellij.application.PlasticContentRevision.getContent(PlasticContentRevision.java:84)
at com.intellij.openapi.vcs.changes.ChangesUtil.loadContentRevision(ChangesUtil.java:367)
at com.intellij.openapi.vcs.changes.FakeRevision.getContentAsBytes(FakeRevision.java:45)
at com.intellij.openapi.vcs.impl.LineStatusTrackerBaseContentUtil.loadContentRevision(LineStatusTrackerBaseContentUtil.java:186)
at com.intellij.openapi.vcs.impl.LineStatusTrackerBaseContentUtil$BaseContentImpl.loadContent(LineStatusTrackerBaseContentUtil.java:147)
at com.intellij.openapi.vcs.impl.BaseRevisionStatusTrackerContentLoader.loadContent(LineStatusTrackerManager.kt:1455)
at com.intellij.openapi.vcs.impl.LineStatusTrackerManager$MyBaseRevisionLoader.loadRequest(LineStatusTrackerManager.kt:557)
at com.intellij.openapi.vcs.impl.LineStatusTrackerManager$MyBaseRevisionLoader.loadRequest(LineStatusTrackerManager.kt:515)
at com.intellij.openapi.vcs.impl.SingleThreadLoader.handleSingleRequest(LineStatusTrackerManager.kt:1314)
at com.intellij.openapi.vcs.impl.SingleThreadLoader.handleRequests(LineStatusTrackerManager.kt:1308)
at com.intellij.openapi.vcs.impl.SingleThreadLoader.access$handleRequests(LineStatusTrackerManager.kt:1188)
at com.intellij.openapi.vcs.impl.SingleThreadLoader$schedule$1$1$1.invokeSuspend$lambda$0(LineStatusTrackerManager.kt:1287)
at com.intellij.openapi.progress.CoroutinesKt.jobToIndicator$lambda$5(coroutines.kt:447)
at com.intellij.openapi.progress.ProgressManager.lambda$runProcess$0(ProgressManager.java:98)
at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$1(CoreProgressManager.java:223)
at com.intellij.platform.diagnostic.telemetry.helpers.TraceKt.use(trace.kt:45)
at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$2(CoreProgressManager.java:222)
at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$executeProcessUnderProgress$14(CoreProgressManager.java:674)
at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:749)
at com.intellij.openapi.progress.impl.CoreProgressManager.computeUnderProgress(CoreProgressManager.java:705)
at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:673)
at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:79)
at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:203)
at com.intellij.openapi.progress.ProgressManager.runProcess(ProgressManager.java:98)
at com.intellij.openapi.progress.CoroutinesKt.jobToIndicator(coroutines.kt:435)
at com.intellij.openapi.progress.CoroutinesKt.contextToIndicator(coroutines.kt:427)
at com.intellij.openapi.progress.CoroutinesKt.coroutineToIndicator(coroutines.kt:371)
at com.intellij.openapi.vcs.impl.SingleThreadLoader$schedule$1$1$1.invokeSuspend(LineStatusTrackerManager.kt:1286)
at com.intellij.openapi.vcs.impl.SingleThreadLoader$schedule$1$1$1.invoke(LineStatusTrackerManager.kt)
at com.intellij.openapi.vcs.impl.SingleThreadLoader$schedule$1$1$1.invoke(LineStatusTrackerManager.kt)
at kotlinx.coroutines.intrinsics.UndispatchedKt.startUndispatchedOrReturn(Undispatched.kt:62)
at kotlinx.coroutines.BuildersKt__Builders_commonKt.withContext(Builders.common.kt:163)
at kotlinx.coroutines.BuildersKt.withContext(Unknown Source)
at com.intellij.openapi.vcs.impl.SingleThreadLoader$schedule$1$1.invokeSuspend(LineStatusTrackerManager.kt:1285)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:104)
at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:608)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:873)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:763)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:750)
I downgraded rider to 2021.1 and then started to receive the error described in this thread. This is absurd. Now I am thinking to change VCS solution
