ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: nobu@ruby-lang.org
To: ruby-core@ruby-lang.org
Subject: [ruby-core:90381] [Ruby trunk Bug#14959] Writing a "link_to" method and a "url_helper" with a request parameter under certain "if else" statement in Rails helper crashes with KERN_INVALID_ADDRESS at 0x0000000000000000
Date: Sun, 09 Dec 2018 02:17:19 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-75491.20181209021718.d653c096fd98e147@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-14959.20180802190009@ruby-lang.org

Issue #14959 has been updated by nobu (Nobuyoshi Nakada).


Seems 2.5.4 has been fixed.

----------------------------------------
Bug #14959: Writing a "link_to" method and a "url_helper" with a request parameter under certain "if else" statement in Rails helper crashes with KERN_INVALID_ADDRESS at 0x0000000000000000
https://bugs.ruby-lang.org/issues/14959#change-75491

* Author: y4m4p (Masahiro Yamashita)
* Status: Closed
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-darwin14]
* Backport: 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN
----------------------------------------
# Disclaimer 
Sorry about the problem being rails, and not ruby specific. I couldn't narrow down the problem and wording it correctly.
As it turns out that the problem derived from the ruby vm used in my Rails application, I decided to create the issue here.

## Backstory
I have created this issue in rails/rails. (https://github.com/rails/rails/issues/33460)
I became aware that this issue derives from Shopify/bootsnap (https://github.com/Shopify/bootsnap/issues/182)
The member there told me that this is an issue with the ruby vm itself, so I have created this issue here.

Please refer for more information in the above link.

# Reproduction
## Reproduction Project:
https://github.com/y4m4p/rails_issue_33460

## Project Dependency
program	version
ruby	        2.5.1p57 (2018-03-29 revision 63029) [x86_64-darwin17]
Rails	5.2.0
Bundler	1.16.1
Mysql	5.7.21 Homebrew

## Reproduction method
~~~ ruby
def helper_method
  if true
    link_to 'page', some_view_path(foo: 'true')
  else
    link_to 'somewhere', some_view_path(foo: 'false')
  end
end
~~~

### Crash condition
Writing this helper method under "app/helper" directory in Rails which satisfies all of the next particular conditions will crash the Rails server application with 
KERN_INVALID_ADDRESS at 0x0000000000000000.

* Writing a condition with
~~~ ruby
if true 
  ... 
else 
  ...
~~~
OR
~~~ ruby
if false 
  ... 
else 
  ...
~~~

* Write a path using the "link_to" helper and a "url_helper (xxx_path)" which contains a "request parameter" (xxx_path(some_parameter: 'x')).
* Writing the process under the statement that will never be used. 
For example, if you write the "if" sentence with "if true" then you must write your process under the "else" statement and vice versa.


### Non crashing condition
* Writing the "if" condition with a instance variable or constant. 
~~~ ruby
def helper_method
  condition = true
  if condition
    ...
  else
    ...
  end
end
~~~

* Do not write the specific "link_to" helper process under the statement that will never be used.
~~~ ruby
def helper_method
  if true
    link_to 'somewhere', web_pages_some_view_path(foo: 'true')
  else
    # link_to 'somewhere', web_pages_some_view_path(foo: 'false')  <= comment out
  end
end
~~~

* Do not write the request parameter for the "url_helper" path.
~~~ ruby
def helper_method
  if true
    link_to 'somewhere', web_pages_some_view_path(foo: 'true') #<= Writing the request parameter in the used statement is OK
  else
    link_to 'somewhere', web_pages_some_other_view_path
  end
end
~~~
* Do not write the process in helper. But rather, writing the process in the view itself will not crash.
~~~ ruby
# app/view/web_pages/some_view.html.erb
<%=  if true
       link_to 'somewhere', web_pages_some_view_path(foo: 'true')
      else
        link_to 'somewhere', web_pages_some_view_path(foo: 'false')
      end %>
~~~
 
## Expected
Should render correct views with link and not crash.
Even though I am writing the "if" condition with "true" which makes the "else" statement useless, but this should work as intended. (Just render the "true" statement.)

---Files--------------------------------
ruby_2018-08-03-030208_y4m4p.crash (63.6 KB)


-- 
https://bugs.ruby-lang.org/

      parent reply	other threads:[~2018-12-09  2:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <redmine.issue-14959.20180802190009@ruby-lang.org>
2018-08-02 19:00 ` [ruby-core:88274] [Ruby trunk Bug#14959] Writing a "link_to" method and a "url_helper" with a request parameter under certain "if else" statement in Rails helper crashes with KERN_INVALID_ADDRESS at 0x0000000000000000 em454ll1lz0
2018-08-02 19:46 ` [ruby-core:88276] " rafaelmfranca
2018-08-03  1:21 ` [ruby-core:88280] " sam.saffron
2018-08-03  7:38 ` [ruby-core:88284] " nobu
2018-09-21  8:17 ` [ruby-core:89118] " ujihisa
2018-09-21  8:36 ` [ruby-core:89119] " nobu
2018-12-05 15:46 ` [ruby-core:90316] " mats
2018-12-09  2:17 ` nobu [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=redmine.journal-75491.20181209021718.d653c096fd98e147@ruby-lang.org \
    --to=ruby-core@ruby-lang.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).