Skip to content
Snippets Groups Projects
  1. Jun 12, 2015
  2. Feb 20, 2015
  3. Feb 19, 2015
    • Lars Kanis's avatar
    • Lars Kanis's avatar
      Discard borrowed object wrappers after method calls into Ruby. · 54a11707
      Lars Kanis authored
      This solves crashes of kind:
      	[BUG] rb_gc_mark(): 0x00000003f54af8 is T_ZOMBIE
      
      All parameters to Ruby event blocks or overloaded methods are converted to
      proper Ruby classes or wrapped by appropriate wrapper classes for borrowed
      objects. The wrapper classes are registered, to keep the connection between
      C-pointer (the borrowed object) and the wrapping Ruby object. This connection
      is canceled either when the borrowed object is destroyed or the Ruby wrapper
      is free'd. If neither of them happens, the wrapper object is re-used for the
      next call.
      
      This worked good with Ruby-1.8, which has one big mark and sweep run.
      Ruby-2.2 introduced incremental GC and has several mark and sweep runs, so
      that marks and sweeps are quite independent. Therefor we re-used objects,
      that are already maked for sweeping (so called T_ZOMBIE).
      
      This patch releases the connection between borrowed object and it's wrapper
      object after each call into Ruby code. Therefore the wrapper object isn't
      re-used, but a new one is created for each param to each call. The wrapper
      objects are later free'd by the GC. This patch could have a negative
      performance impact.
      54a11707
  4. Feb 18, 2015
  5. Feb 17, 2015
  6. Feb 16, 2015
  7. Feb 14, 2015
  8. Jul 09, 2014
  9. Mar 17, 2014
  10. Mar 16, 2014
  11. Mar 15, 2014
  12. Mar 14, 2014
  13. Mar 13, 2014
  14. Dec 20, 2013
  15. Dec 19, 2013
Loading