mafintosh / mafintosh/buffer-reuse-pool
Mem-corruption
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 62
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Just leaving this note here:
I used this lib in a project together with abstract-level and it introduced some spooky action,
I can't really explain what happened but it caused results from the database to suddenly contain data that had never been persisted and was only ever present in the pooled buffers which were used as scratchpads for decoding.
I suspect that the buffer "ownership" was claimed and reused by something else; So I ended up falling back to plain ol' [alloc()](https://github.com/telamon/picotool/commit/b7b56aa5fd6f2dc966f9c3116b3f3ecdca651216#) instead. Point is I shot myself in the foot with premature optimization. :beers:
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
No files or tests are named. Start by reproducing the interaction with abstract-level and buffer-reuse-pool, then trace pooled buffer ownership during database-result decoding. Done means scratchpad data cannot appear in results that were not persisted, with coverage for the failure scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100