Slow memory leak in ibootbar agents when hardware is offline
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 17
- Forks
- 20
- Avg merge
- 1h 22m
- Merged PRs (30d)
- 2
Description
On satp2 there were a bunch of ibootbar agents running for hardware that is currently offline. They, over the course of 30+ days grew to ~7% memory usage each. There were eight running, so this was quite a bit of the memory of the machine.
Seeing as we don't see agents on other platforms running away, I suspect it's something to do with the hardware being offline, like we've seen in other agents (see https://github.com/simonsobs/socs/issues/851 for instance).
My other suspicion is there's something to do with our SNMP implementation, since we had a similar issue with the UPS agents, which we implemented https://github.com/simonsobs/socs/pull/592 as a workaround.
Either way this needs investigation at some point.
socs version: v0.5.3-3-g94412e0-dev
Contributor guide
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 by investigating the ibootbar agents and their SNMP implementation, comparing the behavior with issue #851 and the workaround in pull request #592. Done means identifying the cause of memory growth when hardware is offline, fixing it, and verifying that prolonged offline operation keeps memory usage bounded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100