Actions
Bug #17655
closedExperiencing Repeated Segmentation Faults Using Puma with Ruby 3.0.0
    Bug #17655:
    Experiencing Repeated Segmentation Faults Using Puma with Ruby 3.0.0
  
Description
Issue occurred with Puma and Ruby 3.0.0. I've attached the text scrollback from Puma, it's quite long.
Files
        
           Updated by jlevnhv (Josh Levinson) over 4 years ago
          Updated by jlevnhv (Josh Levinson) over 4 years ago
          
          
        
        
      
      Rails -v 6.1.2.1
        
           Updated by jlevnhv (Josh Levinson) over 4 years ago
          Updated by jlevnhv (Josh Levinson) over 4 years ago
          
          
        
        
      
      This looks like the method which caused the seg fault on line 317
# ~/.rvm/gems/ruby-3.0.0/gems/actionpack-6.1.2.1/lib/action_dispatch/routing/route_set.rb   
--316           def define_url_helper(mod, name, helper, url_strategy)
  317             mod.define_method(name) do |*args|
  318               last = args.last
  319               options = \
  320                 case last
  321                 when Hash
  322                   args.pop
  323                 when ActionController::Parameters
  324                   args.pop.to_h
  325                 end
  326               helper.call(self, name, args, options, url_strategy)
  327             end
  328           end
  329       end
        
           Updated by vo.x (Vit Ondruch) over 4 years ago
          Updated by vo.x (Vit Ondruch) over 4 years ago
          
          
        
        
      
      This reminds me #17536
        
           Updated by jeremyevans0 (Jeremy Evans) over 4 years ago
          Updated by jeremyevans0 (Jeremy Evans) over 4 years ago
          
          
        
        
      
      - Status changed from Open to Feedback
Can you please test with the master branch to see if this issue has been resolved? If it still is present in the master branch, please try to develop a minimal self-contained reproducible example.
        
           Updated by p8 (Petrik de Heus) over 4 years ago
          Updated by p8 (Petrik de Heus) over 4 years ago
          
          
        
        
      
      This seems similar to the following fixed issue: https://bugs.ruby-lang.org/issues/17728
        
           Updated by jeremyevans0 (Jeremy Evans) over 4 years ago
          Updated by jeremyevans0 (Jeremy Evans) over 4 years ago
          
          
        
        
      
      - Status changed from Feedback to Closed
Actions