Issue #10725 has been updated by Daniele Orlandi.


Nobuyoshi Nakada wrote:
> 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.

I understand the difficulties in handling such kind of issues.

I am not able to reproduce the issue in simpler environments but I can try to run gdb while it happens and gather some more info.



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

* Author: Daniele Orlandi
* Status: Feedback
* Priority: Normal
* Assignee: 
* 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/