[ruby-core:68771] [Ruby trunk - Bug #10993] therubyracer-0.12.1/lib/v8/function.rb:13: [BUG] Segmentation fault at 0x30c124 ruby 2.1.5p273 (2014-11-13 revision 48405) [armv7l-linux-eabihf]

Issue #10993 has been updated by Mir S..


Yes! Managed to narrow it down to 'therubyracer' myself. Apparently it's a known issue with ARM devices, essentially the Raspberry Pi 2 and older. Gitlab seems to have the same issues as it relies on it too.
https://github.com/cowboyd/therubyracer/issues/317

To fix this you need to install a precompiled node js package via apt-get or similar and edit your Gemfile and remove (put # before the line) gem 'therubyracer'.

http://stackoverflow.com/questions/29243824/ruby-on-raspberry-pi-2-with-raspbian-webrick-crash-probably-during-asset-compila

I guess we can close this.

----------------------------------------
Bug #10993: therubyracer-0.12.1/lib/v8/function.rb:13: [BUG] Segmentation fault at 0x30c124 ruby 2.1.5p273 (2014-11-13 revision 48405) [armv7l-linux-eabihf]
https://bugs.ruby-lang.org/issues/10993#change-52054

* Author: Mir S.
* Status: Third Party's Issue
* Priority: Low
* Assignee: 
* ruby -v: 2.1.5p273
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
----------------------------------------
I'm trying to install this gem on Raspbian.

Install RBENV and Ruby 2.15 and all is well. I try to launch the server, it starts. I try to access the page, it just sits there, and about a minute later it produces this:

~~~
pi@raspberrypi:~/test$ wagn server
=> Booting WEBrick
=> Rails 3.2.16 application starting in production on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
[2015-03-21 15:44:02] INFO  WEBrick 1.3.1
[2015-03-21 15:44:02] INFO  ruby 2.1.5 (2014-11-13) [armv7l-linux-eabihf]
[2015-03-21 15:44:02] INFO  WEBrick::HTTPServer#start: pid=19774 port=3000
/home/pi/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/therubyracer-0.12.1/lib/v8/function.rb:13: [BUG] Segmentation fault at 0x30c124

(snip)

Aborted
~~~


---Files--------------------------------
bug-10993.log (217 KB)


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