From: turion Date: 2022-11-22T08:37:10+00:00 Subject: [ruby-core:110851] [Ruby master Bug#19140] rb_vm_insn_addr2insn: invalid insn address Issue #19140 has been updated by turion (Manuel B��renz). That's valuable insight! Probably it is a volatile memory fault then. I restarted the physical machine now and I haven't experienced the issue since. ---------------------------------------- Bug #19140: rb_vm_insn_addr2insn: invalid insn address https://bugs.ruby-lang.org/issues/19140#change-100209 * Author: turion (Manuel B��renz) * Status: Open * Priority: Normal * ruby -v: ruby 3.0.4p208 (2022-04-12 revision 3fa771dded) [x86_64-linux] * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN ---------------------------------------- I recently upgraded my mastodon installation to 4.0.2 (and possibly also updated a minor ruby version, not sure) and since then I'm experiencing regular crashes with error messages like: ``` Nov 21 15:25:18 manuelbaerenz puma[1006220]: /nix/store/1m8li3dkfj33kk4xhx6bhjbqi6y9bq6x-mastodon-gems-4.0.2/lib/ruby/gems/3.0.0/gems/activesupport-6.1.7/lib/active_support/json/encoding.rb:58: [BUG] rb_vm_insn_addr2insn: invalid insn address: 0x00007f0646b56e20 ``` An example log with long stacktrace and coredump can be found in https://github.com/mastodon/mastodon/files/10057376/mastodon.log I previously reported this error here where I learned that this must be a Ruby bug: https://github.com/rails/rails/issues/46540 https://github.com/mastodon/mastodon/discussions/21311 -- https://bugs.ruby-lang.org/ Unsubscribe: