Nicolas Rodriguez

@rmzoni what ruby version are you running? it's fixed with version 3.3.5.

> Hi I'm using ruby 3.3.5 and the problem only happens on sidekiq. Weird... I'm using Sidekiq too and doesn't have this issue. It even worked with Ruby < 3.3.5...

> Could you provide your sidekiq version, rails version * ruby 3.3.5 * rails 7.2.1 * puma 6.4.3 (cluster-mode, compacting with `Process.warmup`) * sidekiq 7.3.2 (compacting with `Process.warmup` since 7.2.2...

> Which docker image are you guys using? Weekly home built : debian 12 + ruby built with asdf (ruby-build is used). It's a multiplatform image that works on ARM64...

> are you using eager load on rails? Eager load is by default in production environment.

@tiagotex good catch 👍 I thought it was fixed in Ruby 3.3.5 because before the app failed to start and succeed with 3.3.5. Weirdly I've never had this issue with...

If I run your script with `Process.warmup` instead of `GC.verify_compaction_references(expand_heap: true, toward: :empty)` I've got a different result : `GC.verify_compaction_references(expand_heap: true, toward: :empty)`: ```sh "data" "data" "data" 60 60 80...

@tiagotex Thank you!

@tiagotex linked issue? https://redmine.ruby-lang.org/issues/20853

ping @streamich