keybase / keybase/keybase-issues
Attempt to allocate Buffer larger than maximum size
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
I'm getting the error:
RangeError: Attempt to allocate Buffer larger than maximum size: 0x3fffffff bytes
at new Buffer (buffer.js:71:11)
at Function.Buffer.concat (buffer.js:211:16)
at BufferOutStream.exports.BufferOutStream.BufferOutStream.data (/usr/local/lib/node_modules/keybase/node_modules/iced-spawn/lib/stream.js:102:21)
at /usr/local/lib/node_modules/keybase/node_modules/iced-spawn/lib/cmd.js:484:32
at Deferrals.exports.Deferrals.Deferrals._call (/usr/local/lib/node_modules/keybase/node_modules/iced-runtime/lib/runtime.js:86:16)
at /usr/local/lib/node_modules/keybase/node_modules/iced-runtime/lib/runtime.js:98:26
at exports.trampoline.trampoline (/usr/local/lib/node_modules/keybase/node_modules/iced-runtime/lib/runtime.js:64:14)
at Deferrals.exports.Deferrals.Deferrals._fulfill (/usr/local/lib/node_modules/keybase/node_modules/iced-runtime/lib/runtime.js:96:16)
at ret (/usr/local/lib/node_modules/keybase/node_modules/iced-runtime/lib/runtime.js:29:18)
at SpawnEngine.BaseEngine._maybe_call_callback (/usr/local/lib/node_modules/keybase/node_modules/iced-spawn/lib/cmd.js:57:16)
when I try to decrypt a 950mb file.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the stack trace locations in iced-spawn/lib/stream.js and iced-spawn/lib/cmd.js, then inspect how Buffer.concat is reached during decryption. Reproduce the failure with the reported 950 MB file if available. Done means decrypting that file no longer raises the maximum-buffer-size error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100