Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Cannot Reproduce
    • Affects Version/s: JRuby 1.6.5
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:
      RVM 1.9.2, bundler 1.0.21, OS X Lion
    • Number of attachments :
      0

      Description

      Hi!
      When I start rake in my Rails app with JRuby 1.6.5 with --1.9 it breaks with "stack level too deep". Using -d gives screen after screen of this:

      ...
      at org.jruby.internal.runtime.methods.AliasMethod.call(AliasMethod.java:56)
      at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:133)
      at rubyjit.full_gem_path_C6832BBF145F5FC75E71C0F1D212B0B02F354F9E._file_(/Users/anders.bengtsson/.rvm/gems/jruby-1.6.5/gems/bundler-1.0.21/lib/bundler/rubygems_ext.rb:21)
      at rubyjit.full_gem_path_C6832BBF145F5FC75E71C0F1D212B0B02F354F9E._file_(/Users/anders.bengtsson/.rvm/gems/jruby-1.6.5/gems/bundler-1.0.21/lib/bundler/rubygems_ext.rb)
      at org.jruby.internal.runtime.methods.JittedMethod.call(JittedMethod.java:127)
      at org.jruby.internal.runtime.methods.AliasMethod.call(AliasMethod.java:56)
      at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:133)
      at rubyjit.full_gem_path_C6832BBF145F5FC75E71C0F1D212B0B02F354F9E._file_(/Users/anders.bengtsson/.rvm/gems/jruby-1.6.5/gems/bundler-1.0.21/lib/bundler/rubygems_ext.rb:21)
      at rubyjit.full_gem_path_C6832BBF145F5FC75E71C0F1D212B0B02F354F9E._file_(/Users/anders.bengtsson/.rvm/gems/jruby-1.6.5/gems/bundler-1.0.21/lib/bundler/rubygems_ext.rb)
      at org.jruby.internal.runtime.methods.JittedMethod.call(JittedMethod.java:127)
      at org.jruby.internal.runtime.methods.AliasMethod.call(AliasMethod.java:56)
      at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:133)
      at rubyjit.full_gem_path_C6832BBF145F5FC75E71C0F1D212B0B02F354F9E._file_(/Users/anders.bengtsson/.rvm/gems/jruby-1.6.5/gems/bundler-1.0.21/lib/bundler/rubygems_ext.rb:21)
      at rubyjit.full_gem_path_C6832BBF145F5FC75E71C0F1D212B0B02F354F9E._file_(/Users/anders.bengtsson/.rvm/gems/jruby-1.6.5/gems/bundler-1.0.21/lib/bundler/rubygems_ext.rb)
      at org.jruby.internal.runtime.methods.JittedMethod.call(JittedMethod.java:127)
      at org.jruby.internal.runtime.methods.AliasMethod.call(AliasMethod.java:56)
      Exception `SystemStackError' at org/jruby/RubyArray.java:1612 - stack level too deep

      The code in bundler it gets stuck in looks like this:

      alias_method :rg_full_gem_path, :full_gem_path
      alias_method :rg_loaded_from, :loaded_from

      def full_gem_path
      source.respond_to?(:path) ?
      Pathname.new(loaded_from).dirname.expand_path(Bundler.root).to_s :
      rg_full_gem_path
      end

      This doesn't happen with JRuby 1.6.4 (nor with 1.6.5 in 1.8-mode as far as I can tell).

        Activity

        Hide
        Charles Oliver Nutter added a comment -

        Investigating.

        I forked warbler and enabled JRuby 1.9 mode on travis. No failure! http://travis-ci.org/#!/headius/warbler/builds/2025836

        Continuing...will try jruby-head next, which is in 1.9 mode by default.

        Show
        Charles Oliver Nutter added a comment - Investigating. I forked warbler and enabled JRuby 1.9 mode on travis. No failure! http://travis-ci.org/#!/headius/warbler/builds/2025836 Continuing...will try jruby-head next, which is in 1.9 mode by default.
        Hide
        Charles Oliver Nutter added a comment -

        Attempt number 2...build number 3 against jruby-head, also in 1.9 mode. Also passed... http://travis-ci.org/#!/headius/warbler/builds/2025859

        Moving on to jruby-rack.

        Show
        Charles Oliver Nutter added a comment - Attempt number 2...build number 3 against jruby-head, also in 1.9 mode. Also passed... http://travis-ci.org/#!/headius/warbler/builds/2025859 Moving on to jruby-rack.
        Hide
        Charles Oliver Nutter added a comment -

        I disabled the ENV['TRAVIS'] workaround in my fork of jruby-rack, pushed it, and the travis build succeeded in 1.8 and 1.9 modes: http://travis-ci.org/#!/headius/jruby-rack/builds/2025895

        Is this getting spooky yet?

        I'm starting to wonder if this was a temporary glitch...something wrong in Travis or Bundler or something else.

        Is anyone able to reproduce this today with a repository I can fork?

        Show
        Charles Oliver Nutter added a comment - I disabled the ENV ['TRAVIS'] workaround in my fork of jruby-rack, pushed it, and the travis build succeeded in 1.8 and 1.9 modes: http://travis-ci.org/#!/headius/jruby-rack/builds/2025895 Is this getting spooky yet? I'm starting to wonder if this was a temporary glitch...something wrong in Travis or Bundler or something else. Is anyone able to reproduce this today with a repository I can fork?
        Hide
        Karol Bucek added a comment -

        tried myself with jruby-rack as well - can't seem to reproduce this anymore either.
        hopefully it will last, as it now seems it was a Travis-CI issue after all ...
        thanks for looking into this.

        Show
        Karol Bucek added a comment - tried myself with jruby-rack as well - can't seem to reproduce this anymore either. hopefully it will last, as it now seems it was a Travis-CI issue after all ... thanks for looking into this.
        Hide
        Charles Oliver Nutter added a comment -

        Marking as Cannot Reproduce since the two reproductions that worked before no longer seem to exhibit the problem. Hopefully this one is actually gone for good.

        FYI, there have been other reports of stack overflow in Bundler that are not bug or environment-related but due to Bundler simply using a lot of stack. Those should be reported elsewhere (and already have been in most cases).

        Show
        Charles Oliver Nutter added a comment - Marking as Cannot Reproduce since the two reproductions that worked before no longer seem to exhibit the problem. Hopefully this one is actually gone for good. FYI, there have been other reports of stack overflow in Bundler that are not bug or environment-related but due to Bundler simply using a lot of stack. Those should be reported elsewhere (and already have been in most cases).

          People

          • Assignee:
            Charles Oliver Nutter
            Reporter:
            Anders Bengtsson
          • Votes:
            2 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: