Http.text and Http.header return copies - they handed back the handle's own buffer (and on macOS the response's string), which Http.free released: a text read before the free and used after it was garbage or empty (maroon-lake's maps.json was written with 0 bytes)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
parent
aba5d9e679
commit
359de7bfe5
4 changed files with 19 additions and 4 deletions
6
changes/http-text-copy.md
Normal file
6
changes/http-text-copy.md
Normal file
|
|
@ -0,0 +1,6 @@
|
|||
bump: patch
|
||||
type: fix
|
||||
**`Http.text` and `Http.header` return copies.** They handed back the handle's own buffer (and on macOS the
|
||||
response object's string), which `Http.free` then released: a text read before the free and used after it
|
||||
was garbage or empty - maroon-lake's map list wrote a 0-byte maps.json. Each call now returns a string that
|
||||
is the caller's to keep. Read a body once per response.
|
||||
Loading…
Add table
Add a link
Reference in a new issue