Issue #10725 has been updated by Nobuyoshi Nakada.

Status changed from Open to Feedback

We don't have the same environment equals to yours, we can't address where it happens without the debugging information.
And, as you use some extension libraries, especially ffi, it might be impossible to fix by us.

----------------------------------------
Bug #10725: Segfault with ObjectSpace::trace_object_allocations_start
https://bugs.ruby-lang.org/issues/10725#change-50891

* Author: Daniele Orlandi
* Status: Feedback
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* ruby -v: ruby 2.2.0p0 (2014-12-25 revision 49005) [x86_64-linux-gnu]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
----------------------------------------

While trying to pin down a memory leak issue I enabled trace_object_allocations_start but after a while my application (a daemon, not rails) crashes. I attached the output.



---Files--------------------------------
ruby_crash (136 KB)


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