diff options
| author | Luke Gruber <luke.gruber@shopify.com> | 2025-12-17 13:18:58 -0500 |
|---|---|---|
| committer | John Hawthorn <john@hawthorn.email> | 2025-12-17 11:12:57 -0800 |
| commit | 839410f0734cb3ed911d348855f69ff6d856f62b (patch) | |
| tree | 52c441e97ea459c5557288e630eae9f54cfbc45e /include/ruby/internal/has | |
| parent | 601ac78caf1523170b2f88767d67ffa5e8c5b1bc (diff) | |
Fix heap dump with ractor barrier
When a ractor was being initialized and it would join the heap dump barrier when
allocating its queue or its ports, the heap dump code calls `rb_obj_memsize` on
the ractor and this function assumed `ports` was never NULL. We need to check for
the NULL case in case the ractor is still being initialized. Hopefully other T_DATA
objects don't suffer from the same issue, otherwise we could revert the ractor barrier
during heap dump or not use `rb_obj_memsize` on T_DATA during the heap dump.
Diffstat (limited to 'include/ruby/internal/has')
0 files changed, 0 insertions, 0 deletions