statement "nil.whatever rescue nil" results in building of stack trace
----------------------------------------------------------------------

                 Key: JRUBY-2915
                 URL: http://jira.codehaus.org/browse/JRUBY-2915
             Project: JRuby
          Issue Type: Improvement
          Components: Performance
    Affects Versions: JRuby 1.1.3
         Environment: Any
            Reporter: Greg Fodor
            Priority: Minor


Performing the statement "nil.whatever rescue nil" results in JRuby building a 
full stringified stack trace in memory despite the fact that the exception 
object is never captured. I will update this bug report later with a thread 
dump to confirm this but we were noticing this as a bottleneck in our code due 
to a JDBC driver relying upon a rescue nil to perform normally.

I'd imagine the thread dump should be generated only if there is a 
corresponding node indicating the exception will be caught and manipulated, or 
the stack trace needs to be built more lazily?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to