Details

    • Type: Bug Bug
    • Status: Resolved Resolved
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: JRuby 1.7.0.pre2
    • Fix Version/s: JRuby 1.7.0.RC1
    • Labels:
      None
    • Environment:
      jruby 1.7.0.preview2 (1.9.3p203) 2012-08-07 4a6bb0a on Java HotSpot(TM) Client VM 1.7.0_06-b24 [Windows Server 2008-x86]
    • Number of attachments :
      1

      Description

      Starting a rails application under windows via "jruby -S rails s puma -e production" gives spits out a fatal error. Nevertheless rails comes up and everything seems to run just fine...:

      E:\releases\webcms-20120822-644ffe>jruby -S rails s puma -e production
      Execution protection violation
      #
      # A fatal error has been detected by the Java Runtime Environment:
      #
      #  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x016d3400, pid=3864, tid=3508
      #
      # JRE version: 7.0_06-b24
      # Java VM: Java HotSpot(TM) Client VM (23.2-b09 mixed mode, sharing windows-x86
      )
      # Problematic frame:
      # C  0x016d3400
      #
      # Core dump written. Default location: E:\releases\webcms-20120822-644ffe\hs_err
      _pid3864.mdmp
      #
      # An error report file with more information is saved as:
      # E:\releases\webcms-20120822-644ffe\hs_err_pid3864.log
      #
      # If you would like to submit a bug report, please visit:
      #   http://bugreport.sun.com/bugreport/crash.jsp
      # The crash happened outside the Java Virtual Machine in native code.
      # See problematic frame for where to report the bug.
      #
      
      E:\releases\webcms-20120822-644ffe>=> Booting Puma
      => Rails 3.2.8 application starting in production on http://0.0.0.0:3000
      => Call with -d to detach
      => Ctrl-C to shutdown server
      Puma 1.6.1 starting...
      * Min threads: 0, max threads: 16
      * Environment: production
      * Listening on tcp://0.0.0.0:3000
      

        Activity

        Hide
        Charles Oliver Nutter added a comment -

        Looks like it's problems in our Windows exec implementation. Since the process does seem to come up ok, I would guess something we're doing after creating the subprocess causes JVM to segfault, but otherwise the new process continues ok.

        I do not have a Windows environment to investigate on, but we need to fix this for 1.7.

        Show
        Charles Oliver Nutter added a comment - Looks like it's problems in our Windows exec implementation. Since the process does seem to come up ok, I would guess something we're doing after creating the subprocess causes JVM to segfault, but otherwise the new process continues ok. I do not have a Windows environment to investigate on, but we need to fix this for 1.7.
        Hide
        Falk Pauser added a comment -

        Same error when accessing the registry:

        require "win32/registry"
        Win32::Registry::HKEY_LOCAL_MACHINE.open('SOFTWARE\Microsoft\DirectX')['Version']
        
        Show
        Falk Pauser added a comment - Same error when accessing the registry: require "win32/registry" Win32::Registry::HKEY_LOCAL_MACHINE.open('SOFTWARE\Microsoft\DirectX')['Version']
        Hide
        Charles Oliver Nutter added a comment -

        Fixed by jffi update in RC1.

        Show
        Charles Oliver Nutter added a comment - Fixed by jffi update in RC1.

          People

          • Assignee:
            Charles Oliver Nutter
            Reporter:
            Falk Pauser
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: