From: turion <noreply@ruby-lang.org>
To: ruby-core@neon.ruby-lang.org
Subject: [ruby-core:110851] [Ruby master Bug#19140] rb_vm_insn_addr2insn: invalid insn address
Date: Tue, 22 Nov 2022 08:37:10 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-100209.20221122083709.52567@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-19140.20221121151205.52567@ruby-lang.org
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/
prev parent reply other threads:[~2022-11-22 8:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 15:12 [ruby-core:110838] [Ruby master Bug#19140] rb_vm_insn_addr2insn: invalid insn address turion
2022-11-21 20:52 ` [ruby-core:110845] " alanwu (Alan Wu)
2022-11-22 8:37 ` turion [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-100209.20221122083709.52567@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
--cc=ruby-core@neon.ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).