altstoreio / altstoreio/AltStore
Dynamic RetroAchievements buffer size
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 14.4k
- Forks
- 1.5k
- PR merge metrics
- No merged PRs in 30d
Description
I was playing the Pokémon Unbound Professor Oak Challenge subset and got many messages in the log like this:
RetroAchievements state buffer too small. Need 878092 bytes
It seems that the buffer was initially statically set to 32KiB, and then expanded to 256KiB. The smallest power of 2 able to hold this buffer would be 1MiB, which, if 32KiB was enough at the beginning, would definitely be overkill for most games. Ideally it would be a dynamically allocated buffer to completely eliminate the chance of it being too small.
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
The issue identifies the RetroAchievements state buffer and its current 32 KiB/256 KiB sizing behavior; start by locating that implementation in the Swift project and tracing how the required size is reported. Done means the buffer can accommodate a state larger than the fixed sizes without producing the “buffer too small” message, with relevant coverage added or updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- mobile-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100