googleprojectzero / googleprojectzero/Jackalope
After long-running, the number of executions per second becomes 0.
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.4k
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Description
I used 5 threads and they were running fine at first, but after 40 minutes there was a problem.
Execs/s becomes 0.
Why???
My command line:
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
No source file, test, or entry point is named. Start by reproducing the reported long-running run with the command shown in the issue, then trace how execution rate is calculated and updated as the five threads continue running. Done means identifying why Execs/s reaches 0 and verifying the rate remains accurate during an equivalent extended run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100