JRuby

SystemStackError (stack level too deep) on Java 1.7.0_05

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Not A Bug
  • Affects Version/s: JRuby 1.7.0.pre1
  • Fix Version/s: None
  • Component/s: Ruby 1.8.7
  • Labels:
    None
  • Environment:
  • Number of attachments :
    1

Description

Ran into this issue while trying to make a Rails 2.3.14 application work in above mentioned environment ...

SystemStackError (stack level too deep):
org/jruby/RubyProc.java:269:in `call'
org/jruby/RubyProc.java:219:in `call'
org/jruby/RubyProc.java:269:in `call'
org/jruby/RubyProc.java:219:in `call'
org/jruby/RubyArray.java:1611:in `each'
app/controllers/application_controller.rb:291:in `render_payload'
app/controllers/application_controller.rb:346:in
`render_create_or_error'
app/controllers/messages_controller.rb:61:in `create'
org/jruby/RubyKernel.java:1969:in `send'
org/jruby/RubyKernel.java:1969:in `send'
org/jruby/RubyProc.java:269:in `call'
org/jruby/RubyProc.java:219:in `call'
org/jruby/RubyArray.java:1611:in `each'

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Naga Vijay added a comment -

Here's some backcground on what we have did and what has been working fine for more than a year now - we have customized the to_json for our custom serialization purpose. This custom to_json descends down by way of a recursion, in the sense that it invokes the custom to_json recursively. I must be facing a memory leak mostly with json processing, as I have tried with the bleeding edge jruby source retrieved from GIT repository. Here's the stack trace in ruby console ... see attached.

Show
Naga Vijay added a comment - Here's some backcground on what we have did and what has been working fine for more than a year now - we have customized the to_json for our custom serialization purpose. This custom to_json descends down by way of a recursion, in the sense that it invokes the custom to_json recursively. I must be facing a memory leak mostly with json processing, as I have tried with the bleeding edge jruby source retrieved from GIT repository. Here's the stack trace in ruby console ... see attached.
Hide
Permalink
Naga Vijay added a comment -

This is the attachment that I have referred to in my previous comment.

Show
Naga Vijay added a comment - This is the attachment that I have referred to in my previous comment.
Hide
Permalink
Charles Oliver Nutter added a comment -

Is it possible for you to narrow this to something I can run and reproduce? Without that it's really hard for me to investigate why this would be infinitely recursing.

Show
Charles Oliver Nutter added a comment - Is it possible for you to narrow this to something I can run and reproduce? Without that it's really hard for me to investigate why this would be infinitely recursing.
Hide
Permalink
Naga Vijay added a comment -

Marking this issue as "Not A Bug", as the issue relates to weird json gem version and/or changes to the way json parsing is done. It all realtes to these gems, as far I can tell - cassandra and thrift gems and their use of json gem. We were using json_pure (1.6.1, 1.1.9) in (JRuby 1.6 + Java 6) environment, and now need to use json (1.7.3 java) in (JRuby 1.7 + Java 7) environment.

Show
Naga Vijay added a comment - Marking this issue as "Not A Bug", as the issue relates to weird json gem version and/or changes to the way json parsing is done. It all realtes to these gems, as far I can tell - cassandra and thrift gems and their use of json gem. We were using json_pure (1.6.1, 1.1.9) in (JRuby 1.6 + Java 6) environment, and now need to use json (1.7.3 java) in (JRuby 1.7 + Java 7) environment.

People

  • Assignee:
    Unassigned
    Reporter:
    Naga Vijay
Vote (0)
Watch (4)

Dates

  • Created:
    Updated:
    Resolved: