Unbalanced CoInitialize/CoUninitialize calls
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 58
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
Description
While running wssdagent with Application Verifier in WinDbg we observed the following error:
VERIFIER STOP 0000000000000403: pid 0x2150: Unbalanced CoInitialize/CoUninitialize calls on current thread.
0000000000000000 : Current number of CoInitialize calls on this thread.
0000000000000000 : Previous number of CoInitialize calls on this thread.
0000000000000000 : Stack traces of CoInitialize calls on this thread.
000001953C265FE8 : Stack traces of CoUninitialize calls on this thread.
Jocelyn mentioned that this could be related to the change in https://github.com/microsoft/wmi/pull/11 which removed the StartWMI method.
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
Reproduce wssdagent under Application Verifier in WinDbg and review the change in microsoft/wmi#11 that removed StartWMI. Trace the CoInitialize and CoUninitialize calls involved; done means the calls are balanced and Application Verifier no longer reports the stop.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100