The CF loop causes CPU usage to exceed 100% after [NSApplication run]
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 13
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
When using nodobjc, the cpu usage goes up to 100% once NSApplication('sharedApplication')('run') is issued. Doesn't seem to matter if cf.ref() is executed before or during the application launched delegate callback.
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
Start by reproducing the CPU spike with NSApplication('sharedApplication')('run') and compare behavior when cf.ref() is called before or during the application launched delegate callback. Trace the CFRunLoop integration with the libuv eventloop; done means the application can run without CPU usage exceeding 100% in either cf.ref() case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, node.js
- Domain
- backend, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100