Skip to content
This repository was archived by the owner on Feb 2, 2023. It is now read-only.
This repository was archived by the owner on Feb 2, 2023. It is now read-only.

GC issues #50

@chancancode

Description

@chancancode

If we:

  1. heap allocate a struct-based helix object (e.g. Duration::new)
  2. GC runs

It will GC the Ruby object associated with the helix object, because the GC couldn't see the VALUE pointer on the stack

See sparklemotion/nokogiri@0a1556a
and http://blog.reverberate.org/2016/06/12/native-extensions-memory-management-part1-ruby-mri.html

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions