FID leak
Open
Nobody has claimed this yet.
- Dominant language
- OCaml
- Stars
- 1.2k
- Forks
- 214
- PR merge metrics
- No merged PRs in 30d
Description
When hyperkit exits and restarts in a loop I see lots of these:
2016-12-09 ... <Notice>: FID pool exhausted (will wait for a free one; deadlock possible)
Perhaps there's a failure to clean up a connection or a FID somewhere? I would have thought the FID pool was per connection but perhaps there's a problem there.
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 reproducing the hyperkit exit-and-restart loop and observe the FID pool exhausted notice. Trace connection and FID cleanup around the restart path; done means the loop no longer exhausts the pool or leaves FIDs unreleased.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100