[jira] [Created] (GROOVY-8324) Enabling groovy.indy.logging can lead to stack overflows

["Matt Whipple (JIRA)" <ji...@apache.org>]

Matt Whipple created GROOVY-8324:
------------------------------------

             Summary: Enabling groovy.indy.logging can lead to stack overflows
                 Key: GROOVY-8324
                 URL: https://issues.apache.org/jira/browse/GROOVY-8324
             Project: Groovy
          Issue Type: Bug
            Reporter: Matt Whipple


Still digging through this a bit more, but while trying to diagnose performance issues I enabled indy logging which led to:
{noformat}
! Caused by: java.lang.StackOverflowError: null
! at java.lang.Class.getEnclosingMethodInfo(Class.java:1072)
! at java.lang.Class.getEnclosingClass(Class.java:1272)
! at java.lang.Class.getSimpleBinaryName(Class.java:1443)
! at java.lang.Class.getSimpleName(Class.java:1309)
! at java.lang.invoke.MethodType.toString(MethodType.java:797)
! at java.lang.String.valueOf(String.java:2982)   <--- Loops back to here
! at java.lang.StringBuilder.append(StringBuilder.java:131)
! at org.codehaus.groovy.vmplugin.v7.Selector$MethodSelector.<init>(Selector.java:488)
! at org.codehaus.groovy.vmplugin.v7.Selector.getSelector(Selector.java:98)
! at org.codehaus.groovy.vmplugin.v7.IndyInterface.selectMethod(IndyInterface.java:227)
! at MyDomainClass.toString(MyDomainClass.groovy)
{noformat}

The class itself stringifies without issue, I'm presently changing it to use {{@CompileStatic}} but it might be nice if that specific log message could be toggled independently of the others to try to avoid the possibility of blowing up while attempting to troubleshooting. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)