KhronosGroup / KhronosGroup/OpenCL-Docs
what is the mean of reference count?
- Dominant language
- Python
- Stars
- 420
- Forks
- 131
- Avg merge
- 5d 13h
- Merged PRs (30d)
- 11
Description
I read the OpenCL manual and found that reference counts vary depending on the underlying implementation, but they must return to zero after being released.
However, I'm still confused about reference counts.
The OpenCL manual indicates that they can be used to detect memory leaks. How exactly do we do this?
We'd like to use this to detect memory leaks, but we can't find a standard method.
Theoretically, interface users can't access a released object, so how can we detect that it must return to zero after being released?
If reference counts can't be used to detect memory leaks, then it seems meaningless to OpenCL users. What's the point of providing them to the public?
Contributor guide
Research direction
Start with the OpenCL manual sections on reference counts and object release. No file, test, or entry point is named in the issue; done would require clarifying whether reference counts can detect memory leaks and documenting a standard method for users, if one exists.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100