From: "luke-gru (Luke Gruber) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "luke-gru (Luke Gruber)" <noreply@ruby-lang.org>
Subject: [ruby-core:116800] [Ruby master Bug#20271] Issue with moving embedded string across ractors
Date: Fri, 16 Feb 2024 16:34:21 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-106822.20240216163421.3573@ruby-lang.org> (raw)
In-Reply-To: <redmine.issue-20271.20240216162935.3573@ruby-lang.org>
Issue #20271 has been updated by luke-gru (Luke Gruber).
PR here: https://github.com/ruby/ruby/pull/9993
----------------------------------------
Bug #20271: Issue with moving embedded string across ractors
https://bugs.ruby-lang.org/issues/20271#change-106822
* Author: luke-gru (Luke Gruber)
* Status: Open
* Priority: Normal
* Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN
----------------------------------------
When embedded strings are moved, the embedded bytes aren't copied over to the new embedded string. This shows itself when
an embedded string has more than 16 characters, and can also be a problem when the MovedObject has been garbage collected
and another object has taken its place in the ruby heap.
For example:
```ruby
r = Ractor.new {
foo = receive
puts foo
foo
}
obj = "12345678" * 3
puts obj
r.send(obj, move: true)
r.take
```
```
123456781234567812345678
1234567812345678
```
--
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/postorius/lists/ruby-core.ml.ruby-lang.org/
next prev parent reply other threads:[~2024-02-16 16:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 16:29 [ruby-core:116799] " luke-gru (Luke Gruber) via ruby-core
2024-02-16 16:34 ` luke-gru (Luke Gruber) via ruby-core [this message]
2024-09-20 11:08 ` [ruby-core:119270] " hsbt (Hiroshi SHIBATA) via ruby-core
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-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-106822.20240216163421.3573@ruby-lang.org \
--to=ruby-core@ml.ruby-lang.org \
--cc=noreply@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 NNTP newsgroup(s).