Ruby Issue Tracking System

07/09/2026

09:43 AM Ruby Revision d65b0ec0 (git): [ruby/json] Avoid re-decoding an incomplete number on every ResumableParser chunk

`JSON::ResumableParser` re-decodes an incomplete number on every chunk it
receives, so a long number delivered in small chunks is disproportionately slow
to parse -- the work is quadratic (a bit worse in practice) in the number's
length.... pocke (Masataka Kuwabara)

05:57 AM Ruby Revision f3f3270f (git): [ruby/json] Fix ResumableParser losing tokens before a feed-boundary suspension

When a feed boundary fell right after a consumed token -- a `,` or an opening
`[` / `{` -- whose effect was not yet committed to the parser's persistent
state, the token was dropped on resume, producing parse errors or silently
wrong val... pocke (Masataka Kuwabara)

07/03/2026

09:22 AM Ruby Revision 31bf04b4 (git): [ruby/json] Fix ResumableParser treating unterminated line comments as complete

A `//` line comment split across a feed boundary was treated as fully
consumed, so comment body delivered in a later chunk leaked out as parsed
JSON values.
## Reproduction
```ruby
require "json"
parser = JSON::ResumableParser.new(all... pocke (Masataka Kuwabara)

06/22/2026

07:51 AM Ruby Revision 2f65ce7c (git): [ruby/json] Preserve UTF-8 encoding when reallocating a frozen ResumableParser buffer

`JSON::ResumableParser#<<` raises `Encoding::CompatibilityError` when the
first chunk is a frozen multibyte UTF-8 string and more data is fed after a
partial parse.
## Reproduction
```ruby
require "json"
parser = JSON::ResumableParser... pocke (Masataka Kuwabara)

02/14/2025

07:32 AM Ruby Bug #21127 (Closed): Thread deadlock does not display backtraces

Applied in changeset commit:git|0cab608d3a7791c229eea2ebe276494f063c8176.
----------
[Bug #21127] Thread deadlock does not display backtraces (#12721)
Previously, Ruby displayed backtraces for each thread on deadlock. However, it has n... pocke (Masataka Kuwabara)

07:31 AM Ruby Revision 0cab608d (git): [Bug #21127] Thread deadlock does not display backtraces (#12721)

Previously, Ruby displayed backtraces for each thread on deadlock. However, it has not been shown since Ruby 3.0.
It should display the backtrace for debugging.
Co-authored-by: Jeremy Evans <code@jeremyevans.net> pocke (Masataka Kuwabara)

02/10/2025

07:53 AM Ruby Bug #21127 (Closed): Thread deadlock does not display backtraces

Previously, Ruby displayed backtraces for each thread on deadlock. However, it has not been shown since Ruby 3.0.
It should display the backtrace for debugging. (related: https://bugs.ruby-lang.org/issues/8214)
## Step to reproduce
... pocke (Masataka Kuwabara)

01/02/2025

04:40 PM Ruby Revision 2f067447 (git): [ruby/prism] Fix cross-compile issue with newlib on Ubuntu 24.04

https://github.com/ruby/prism/commit/61ebe51233 pocke (Masataka Kuwabara)

09/09/2024

07:25 AM Ruby Bug #20710: Reducing Hash allocation introduces large performance degradation (probably related to VWA)

@peterzhu2118 Thanks for your work! I've confirmed this PR improves the performance in my environment too. pocke (Masataka Kuwabara)

09/02/2024

06:24 AM Ruby Bug #20710 (Closed): Reducing Hash allocation introduces large performance degradation (probably related to VWA)

I found a surprising performance degradation while developing RBS.
In short, I tried to remove unnecessary Hash allocations for RBS. Then, it made the execution time 2x slower.
VWA for Hash probably causes this degradation. I'd be ha... pocke (Masataka Kuwabara)