nosj 0.4.0-x86_64-linux → 0.4.1-x86_64-linux

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: effa3ad5689bc6b7db21ff87769eb797fb7a5930ed8859b4ff7537e70a8301f4
-  data.tar.gz: 3c0d90a1732b7ec4db785a91754cea7bb0eb2cd97802eaeb3b3018ea45c0e884
+  metadata.gz: 1b1ee57c8d059a5906baba48a25a9cd0ddb58c259110e62b6ce6fe3ba4377e0f
+  data.tar.gz: 312af7ca03bb1ea8bf65d8f55d68d4e5a49f8ebccc512246cd14b6652ddf6f09
 SHA512:
-  metadata.gz: d54505db98dde8ba148900bae939ef2db8f1d95ca9e837d7acd2eb8efde5dc51f7b576faa5ee79ddf2b306e79ca5dc5c8330760d9521cb076c3c482a38e93a66
-  data.tar.gz: cfd0a649d0afd2c6f18d0ba11e1293fd2bf7030d4d103e23ff8c68df9519308d99660edd4c431eb0fbddd35ed9959e8bff969e9918fac2a1293884772d7cf114
+  metadata.gz: 7f5cec4abab64a013bddbee26c0813750c3d66942dcb94c50c54f499e0d34e5515b34ffe8f2e4cf1ebc6e4c3647604120e3003194f4f87637d8230314e4eecfc
+  data.tar.gz: 7916c28d532c41a458d8b0b6aa7e6d37a411574728a0b44e7d526dd397bdd6ce8627060a3255ce4f7685931ee778f67c11fa206af97df9d432e1929d89c168ba

data/CHANGELOG.md

@@ -1,3 +1,47 @@
+## [0.4.1] - 2026-09-25
+
+- Fixed a crash in `NOSJ.generate`: an object whose `to_json` or
+  `to_s` shrank the array being generated (for example with
+  `Array#clear`) made the generator read freed memory, usually a
+  segfault. The array length is now re-read for every element, like
+  the json gem, so elements a callback appends are emitted too.
+- Fixed memory corruption in `NOSJ.splice`: a replacement value whose
+  `to_json` modified the source string, deduplicated a frozen String
+  subclass (`-str`), or removed entries from the edits hash could make
+  splice read freed memory, copying unrelated heap bytes into the
+  result or crashing. All values are now generated before the source
+  is read.
+- Fixed `NOSJ.lazy` and `NOSJ.each_line` reading freed memory when the
+  source is a frozen String subclass (such as
+  `ActiveSupport::SafeBuffer`) or a frozen string carrying instance
+  variables, and it is deduplicated with `-str` while the lazy
+  document is alive or between lines: Ruby swaps such a string's
+  buffer, and the old one kept being read (wrong values, or a crash).
+- Fixed a memory leak in `NOSJ.generate` and `NOSJ.write_file`: an
+  exception raised by user code the generator calls bypassed its
+  cleanup and leaked its output buffer (megabytes per call after large
+  documents). Affected: a raising `respond_to?` or
+  `respond_to_missing?`, a raising `to_s` on an encoding-conversion
+  error, a raising autoload of `JSON::Fragment` (strict and Rails
+  modes), and a raising `Errno` constructor for a failed write. The
+  exception still propagates unchanged.
+- Fixed: after a `NoMemoryError` in the middle of a parse (or
+  `minify`/`reformat`), the next call on that thread aborted the whole
+  process. Per-thread parser state is now recovered instead.
+- `NOSJ::Lazy` nodes now take part in generational GC: holding many
+  nodes no longer slows down every minor GC (200,000 live nodes: 2.9 ms
+  per minor GC before, 0.1 ms now), and they are freed immediately
+  when collected.
+- Fixed: lazy documents opened with `allow_trailing_comma: true` or
+  `allow_nan: true` could not be walked. `size`, `keys`, `each`, and
+  any lookup that missed or stepped over a trailing comma or a `NaN`
+  raised `NOSJ::ParserError`, even though `value` worked.
+- `NOSJ.at_pointer`, `NOSJ.at_pointers`, and `NOSJ.at_pointer_file`
+  now honor `allow_nan` and `allow_trailing_comma` while resolving the
+  pointer, not only when materializing the matched value.
+- Updated the nosj crate to 0.2.2.
+- Updated dependencies, Magnus bumped to 0.9.0.
+
 ## [0.4.0] - 2026-09-05
 
 - Ractors: on Ruby 4.0+, `NOSJ.parse`, `NOSJ.generate`, and every

data/README.md

@@ -151,7 +151,8 @@ Example: an early field resolves in ~0.35µs where `JSON.parse(json).dig(...)`
 costs ~980µs on the same document—three orders of magnitude. A field
 at the far end of a 570 KB document costs ~71µs, still 13× faster
 than parse-then-dig. Misses return nil; matched subtrees materialize
-with the same options as `parse` (`symbolize_names:`, `freeze:`).
+with the same options as `parse` (`symbolize_names:`, `freeze:`), and
+`allow_nan:`/`allow_trailing_comma:` govern the walk to them too.
 
 ### Files API
 

data/lib/nosj/version.rb

@@ -2,5 +2,5 @@
 
 module NOSJ
   # The gem version.
-  VERSION = "0.4.0"
+  VERSION = "0.4.1"
 end

data/lib/nosj.rb

@@ -205,7 +205,8 @@ module NOSJ
 
   # Partial parsing by JSON Pointer (with the standard +~0+/+~1+
   # escapes). The matched subtree materializes under the same options
-  # as {.parse}.
+  # as {.parse}; +allow_nan+ and +allow_trailing_comma+ also govern the
+  # walk to it.
   #
   # @example
   #   NOSJ.at_pointer(json, "/users/3/name")  #=> "grace" or nil

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: nosj
 version: !ruby/object:Gem::Version
-  version: 0.4.0
+  version: 0.4.1
 platform: x86_64-linux
 authors:
 - Yaroslav Markin
@@ -66,7 +66,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: 3.3.11
 requirements: []
-rubygems_version: 4.0.16
+rubygems_version: 4.0.20
 specification_version: 4
 summary: An extremely fast JSON parser and generator for Ruby, written in Rust and
   SIMD-accelerated on every platform.