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

Notification

Icon
Error
Exception thrown in Rider running version 5.14.0.5
Options
Previous Topic Next Topic
lassesjorup
#1 Posted : Monday, May 12, 2025 7:21:01 AM(UTC)
Rank: Member

Groups: Registered
Joined: 12/17/2012(UTC)
Posts: 10
Location: Denmark

Thanks: 1 times
Was thanked: 4 time(s) in 4 post(s)
Hey. Thank you for your indispensable tool.

In Rider i get the following IDE internal errors once or twice a day. The IDE stalls for 10-15 seconds but neither Rider or NCrunch stops working. There appears to be no clear pattern in when this appears.

Have a nice day.

java.lang.Throwable: Do not call `getChildren(null)`. Do not expand action groups manually. Reuse `AnActionEvent.updateSession` by composing, wrapping, and postprocessing action groups. Otherwise, use `getChildActionsOrStubs()` or `getChildren(ActionManager)`
at com.intellij.openapi.diagnostic.Logger.error(Logger.java:375)
at com.intellij.openapi.actionSystem.DefaultActionGroup.reportGetChildrenForNullEvent(DefaultActionGroup.java:373)
at com.intellij.openapi.actionSystem.DefaultActionGroup.getChildren(DefaultActionGroup.java:367)
at com.remco.software.ncrunch.NCrunchStartupActivity.updateMenuActionsRecursively(NCrunchStartupActivity.kt:118)
at com.remco.software.ncrunch.NCrunchStartupActivity.execute(NCrunchStartupActivity.kt:90)
at com.intellij.ide.startup.impl.StartupManagerImplKt$launchActivity$1.invokeSuspend(StartupManagerImpl.kt:493)
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)

java.lang.Throwable: Do not call `getChildren(null)`. Do not expand action groups manually. Reuse `AnActionEvent.updateSession` by composing, wrapping, and postprocessing action groups. Otherwise, use `getChildActionsOrStubs()` or `getChildren(ActionManager)`
at com.intellij.openapi.diagnostic.Logger.error(Logger.java:375)
at com.intellij.openapi.actionSystem.DefaultActionGroup.reportGetChildrenForNullEvent(DefaultActionGroup.java:373)
at com.intellij.openapi.actionSystem.DefaultActionGroup.getChildren(DefaultActionGroup.java:367)
at com.remco.software.ncrunch.NCrunchStartupActivity.updateMenuActionsRecursively(NCrunchStartupActivity.kt:118)
at com.remco.software.ncrunch.NCrunchStartupActivity.updateMenuActionsRecursively(NCrunchStartupActivity.kt:119)
at com.remco.software.ncrunch.NCrunchStartupActivity.execute(NCrunchStartupActivity.kt:90)
at com.intellij.ide.startup.impl.StartupManagerImplKt$launchActivity$1.invokeSuspend(StartupManagerImpl.kt:493)
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)
Back to top
willdean
#2 Posted : Monday, May 12, 2025 8:53:21 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 1/31/2012(UTC)
Posts: 33
Location: England

Thanks: 8 times
Was thanked: 4 time(s) in 4 post(s)
I came here to report these. This didn't start with the latest nCrunch - but it might have started with Rider 2025. Rider tells us to report this to you - the report to JB buttons are greyed-out.
Back to top
Remco
#3 Posted : Monday, May 12, 2025 11:07:10 AM(UTC)
Rank: NCrunch Developer

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

Thanks: 990 times
Was thanked: 1329 time(s) in 1232 post(s)
Thanks for sharing these. These errors started showing up with Rider 2025.1. As far as I can tell, they don't seem to have a functional impact on the IDE - They seem to be warning about an API misuse; something that should be corrected to implement best practice.

Did the errors seem to be triggered with your performance issue? Or did you find them in the log after you went searching for a reason?
Back to top
lassesjorup
#4 Posted : Thursday, May 15, 2025 11:38:56 AM(UTC)
Rank: Member

Groups: Registered
Joined: 12/17/2012(UTC)
Posts: 10
Location: Denmark

Thanks: 1 times
Was thanked: 4 time(s) in 4 post(s)
Hey Remco.

I did first notice the issue after upgrading to 2025.1. I currently have 2025.1.2 installed and still se the issue. After the 10-15 second stall the IDE and NCrunch plugin continues to run unaffected, but the stall is a little annoying ;)

It is hard to tell if it is triggered by or triggers the performance issue, but the error timestamp and the time of the performance degradation overlap.

Lasse
Back to top
Remco
#5 Posted : Thursday, May 15, 2025 11:47:22 AM(UTC)
Rank: NCrunch Developer

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

Thanks: 990 times
Was thanked: 1329 time(s) in 1232 post(s)
Does Rider give you an opportunity to dump the call stack when the stall happens? It would be rather perplexing to see the stall being related to this error. I do intend to look at fixing the error, but solving the stall is going to require much more detailed information.
Back to top
lassesjorup
#6 Posted : Thursday, May 15, 2025 11:51:55 AM(UTC)
Rank: Member

Groups: Registered
Joined: 12/17/2012(UTC)
Posts: 10
Location: Denmark

Thanks: 1 times
Was thanked: 4 time(s) in 4 post(s)
I don't think I can dump the call stack but I will se what intel I can gather next time it happens.
Back to top
1 user thanked lassesjorup for this useful post.
Remco on 5/15/2025(UTC)
Remco
#7 Posted : Friday, May 16, 2025 5:06:29 AM(UTC)
Rank: NCrunch Developer

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

Thanks: 990 times
Was thanked: 1329 time(s) in 1232 post(s)
Back to top
lassesjorup
#8 Posted : Sunday, May 18, 2025 7:44:46 PM(UTC)
Rank: Member

Groups: Registered
Joined: 12/17/2012(UTC)
Posts: 10
Location: Denmark

Thanks: 1 times
Was thanked: 4 time(s) in 4 post(s)
Right now I suspect the stall is caused by Rider collecting information about the issue and not the issue itself. I have installed the fix and will give it a spin tomorrow and report back.
Back to top
Remco
#9 Posted : Sunday, May 18, 2025 11:09:27 PM(UTC)
Rank: NCrunch Developer

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

Thanks: 990 times
Was thanked: 1329 time(s) in 1232 post(s)
lassesjorup;18141 wrote:
Right now I suspect the stall is caused by Rider collecting information about the issue and not the issue itself. I have installed the fix and will give it a spin tomorrow and report back.


That would make sense. I'm keen to hear whether it solves the problem for you (I can't seem to get it to happen on my end).
Back to top
lassesjorup
#10 Posted : Wednesday, May 21, 2025 7:28:35 AM(UTC)
Rank: Member

Groups: Registered
Joined: 12/17/2012(UTC)
Posts: 10
Location: Denmark

Thanks: 1 times
Was thanked: 4 time(s) in 4 post(s)
I have been running the new version and the issue and the stall seems to be resolved. :)
Thank you
Back to top
1 user thanked lassesjorup for this useful post.
Remco on 5/21/2025(UTC)
lassesjorup
#11 Posted : Wednesday, May 21, 2025 12:42:58 PM(UTC)
Rank: Member

Groups: Registered
Joined: 12/17/2012(UTC)
Posts: 10
Location: Denmark

Thanks: 1 times
Was thanked: 4 time(s) in 4 post(s)
Reverted back to the previous version and the issue returned (as expected ;)).
Did manage to catch a glims of a "dumping stacktrace"ish message from Rider while the stall was happening so I am quite sure that it is whats causing the stall.
Back to top
Remco
#12 Posted : Wednesday, May 21, 2025 11:35:04 PM(UTC)
Rank: NCrunch Developer

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

Thanks: 990 times
Was thanked: 1329 time(s) in 1232 post(s)
lassesjorup;18147 wrote:
Reverted back to the previous version and the issue returned (as expected ;)).
Did manage to catch a glims of a "dumping stacktrace"ish message from Rider while the stall was happening so I am quite sure that it is whats causing the stall.


Excellent, thanks for confirming this. I'll admit that I didn't expect this, but it's one of those situations where I'm happiest being wrong :)
Back to top
Users browsing this topic
Guest
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.072 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download