Bug #5619

Segfault on OS X

Added by Otto Hilska over 2 years ago. Updated over 1 year ago.

[ruby-core:40943]
Status:Closed
Priority:Normal
Assignee:Kenta Murata
Category:-
Target version:2.0.0
ruby -v:ruby 2.0.0dev (2012-03-10 trunk 34964) [x86_64-darwin11.3.0] Backport:

Description

When I run 'roadie' gem specs on OS X, Ruby 1.9.3p0 segfaults.

Here's how to reproduce:

$ rvm use 1.9.3
$ git clone git://github.com/Mange/roadie.git
$ cd roadie
$ bundle install
$ bundle exec rake

I've attached the command output and the crash report.

It seems it might be a nokogiri issue, but since nokogiri's own tests run fine, I'm not sure.

This is my environment:

$ uname -a
Darwin becherovkax.local 11.2.0 Darwin Kernel Version 11.2.0: Tue Aug 9 20:54:00 PDT 2011; root:xnu-1699.24.8~1/RELEASEX8664 x8664
$ ruby -v
ruby 1.9.3p0 (2011-10-30 revision 33570) [x86
64-darwin11.2.0]

It also happens with current 1.9.3-head (installed from RVM):
ruby 1.9.3p0 (2011-11-08 revision 33661) [x86_64-darwin11.2.0]

However, everything works fine on Linux.

roadie-crash.txt Magnifier - Console output with a stacktrace (74.9 KB) Otto Hilska, 11/11/2011 11:18 PM

osx_ruby_crash_report_roadie.crash - OS X crash report (15.9 KB) Otto Hilska, 11/11/2011 11:18 PM

valgrind-log.txt Magnifier - valgrind run output (219 KB) Otto Hilska, 11/13/2011 08:27 PM

ruby_2011-11-14-154022_valo-mac.crash - OS X crash report (19.6 KB) Valentin Mihov, 11/14/2011 10:48 PM

crash_output.txt Magnifier - crash output (72.7 KB) Valentin Mihov, 11/14/2011 10:48 PM

History

#1 Updated by Motohiro KOSAKI over 2 years ago

Seems memory curruption issue.
Can you try valgrind or other memory error detection tools?

#2 Updated by Nobuyoshi Nakada over 2 years ago

Seems libxml related finalizer issue.

#3 Updated by Otto Hilska over 2 years ago

Here's what I get running valgrind. Let me know if I should enable some extra checks.

#4 Updated by Motohiro KOSAKI over 2 years ago

  • ruby -v changed from ruby 1.9.3p0 (2011-10-30 revision 33570) [x86_64-darwin11.2.0] to -

File valgrind-log.txt added

Here's what I get running valgrind. Let me know if I should enable some extra checks.

Hmmm.. This seems to don't have a useful hint.

#5 Updated by Valentin Mihov over 2 years ago

I verified the segmentation fault on the same version of OS X with ruby 1.9.3. I am attaching the crash report from OS X and the output on the command line. I will try later to run it through valgrind and see if I can find anything there...

#6 Updated by Kenta Murata about 2 years ago

  • Assignee set to Kenta Murata

#7 Updated by Kenta Murata about 2 years ago

  • Target version changed from 1.9.3 to 2.0.0
  • ruby -v changed from - to ruby 2.0.0dev (2012-03-10 trunk 34964) [x86_64-darwin11.3.0]

#8 Updated by Shyouhei Urabe about 2 years ago

  • Status changed from Open to Assigned

#9 Updated by Kenta Murata over 1 year ago

  • Status changed from Assigned to Closed

I couldn't reproduce this issue on the latest trunk, r38731.
It may be fixed on the current trunk, I think.

Also available in: Atom PDF