ruby.git/test/objspace/test_objspace.rb, branch v3_4_9

Check whether object is valid in allocation_info_tracer_compact

2024-12-16T17:24:24+00:00

When reference updating ObjectSpace.trace_object_allocations, we need to
check whether the object is valid or not because it does not mark the
object so the object may be dead. This can cause a segmentation fault
if the object is on a free heap page.

For example, the following script crashes:

    require "objspace"

    objs = []
    ObjectSpace.trace_object_allocations do
      1_000_000.times do
        objs << Object.new
      end
    end

    objs = nil

    # Free pages that the objs were on
    GC.start

    # Run compaction and check that it doesn't crash
    GC.compact

Fix ObjectSpace.trace_object_allocations for compaction

2024-12-16T15:12:54+00:00

We need to reinsert into the ST table when an object moves because it is
a numtable that hashes on the object address, so when an object moves we
need to reinsert it rather than just updating the key.

ObjectSpace.dump: handle Module#set_temporary_name

2024-11-12T19:21:27+00:00

[Bug #20892]

Until the introduction of that method, it was impossible for a
Module name not to be valid JSON, hence it wasn't going through
the slower escaping function.

This assumption no longer hold.

Replace all GC.disable with EnvUtil.without_gc

2024-09-17T14:34:26+00:00

[Feature #20470] Split GC into gc_impl.c

2024-07-03T13:03:40+00:00

This commit splits gc.c into two files:

- gc.c now only contains code not specific to Ruby GC. This includes
  code to mark objects (which the GC implementation may choose not to
  use) and wrappers for internal APIs that the implementation may need
  to use (e.g. locking the VM).

- gc_impl.c now contains the implementation of Ruby's GC. This includes
  marking, sweeping, compaction, and statistics. Most importantly,
  gc_impl.c only uses public APIs in Ruby and a limited set of functions
  exposed in gc.c. This allows us to build gc_impl.c independently of
  Ruby and plug Ruby's GC into itself.

Stabilize TestObjSpace#test_dump_special_consts

2024-05-09T10:23:34+00:00

The test assumes `:foo` is a static symbol, but that is only true
if a literal `:foo` was parsed before `"foo".to_sym` was evaled:

```ruby
require 'objspace'
foo_sym = "foo".to_sym
puts ObjectSpace.dump(eval(":foo"))
```

```
{"address":"0x100fb46d0", "type":"SYMBOL", "shape_id":10, "slot_size":40, "class":"0x100d3e9c8", "frozen":true, "bytesize":3, "value":"foo", "memsize":40, "flags":{"wb_protected":true, "marking":true, "marked":true}}
```

Ensure test suite is compatible with --frozen-string-literal

2024-03-14T16:56:15+00:00

As preparation for https://bugs.ruby-lang.org/issues/20205
making sure the test suite is compatible with frozen string
literals is making things easier.

Skip a flaky objspace test on Visual Studio

2023-12-07T17:42:56+00:00

This seems to happen only on VisualStudio:
https://github.com/ruby/ruby/actions/runs/7130917319/job/19418375386

It fails relatively frequently. Nobody seems actively working on it, so
let's skip it until somebody starts working on it.

objspace_dump.c: dump call cache ids with dump_append_id

2023-11-22T09:24:35+00:00

Not all `ID` have an associated string.

Fixes a SEGFAULT in ObjectSpace.dump_all spec.

Revert "Fix crash caused by concurrent ObjectSpace.dump_all calls"

2023-11-13T07:57:57+00:00

This reverts commit 9a62fd3cbae2ebb60e2f9cad782af1ad18db4319.