From: "alanwu (Alan Wu) via ruby-core" Date: 2025-01-15T19:58:45+00:00 Subject: [ruby-core:120704] [Ruby master Bug#21021] "try to mark T_NONE object" with 3.4.1 Issue #21021 has been updated by alanwu (Alan Wu). T_NONE on the stack is reminiscent of a class of YJIT bugs we see during development. I recommend building Ruby while passing `--enable-yjit=dev` to `./configure` then attempting to re-trigger the crash. This build configuration runs debug assertions that can reveal more information about the bug. Note that you'll need `cargo` for this development build configuration and the build process will download some Rust dependencies from the internet. If you use a third-party tool to build Ruby, you'll need to pass options to `./configure` through that tool. * For `ruby-install`, it's `$ ruby-install -- --enable-yjit=dev` * For `ruby-build`, you can use the `CONFIGURE_OPTS` environment variable, e.g `$ CONFIGURE_OPTS=--enable-yjit=dev ruby-build ....` You should be able to verify that you have a dev build by checking `$ ruby --yjit -v`. It should include "+YJIT dev" like the following: ruby 3.4.1 (2024-12-25 revision 48d4efcb85) +YJIT dev +PRISM [arm64-darwin24] ---------------------------------------- Bug #21021: "try to mark T_NONE object" with 3.4.1 https://bugs.ruby-lang.org/issues/21021#change-111538 * Author: Benoit_Tigeot (Benoit Tigeot) * Status: Open * ruby -v: ruby 3.4.1 (2024-12-25 revision 48d4efcb85) +YJIT +PRISM [x86_64-linux] ��� * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- Hello We upgraded to 3.4.1 yesterday but we are seeing crash since then. ``` /bundle/ruby/3.4.0/gems/activejob-7.2.2.1/lib/active_job/enqueuing.rb:93: [BUG] try to mark T_NONE object ``` I saw the other issue related to ffi gem https://bugs.ruby-lang.org/issues/20694 But in our case the `C level backtrace information` looks different. https://gist.github.com/benoittgt/13507c2000281aa7740bc782adab68c5 We migrated this part of the code to parallel->concurrent-ruby and we do not see the error yet again but I am a little bit worried we could see the issue again. -- https://bugs.ruby-lang.org/ ______________________________________________ ruby-core mailing list -- ruby-core@ml.ruby-lang.org To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/