Possibility to improve macOS support?
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 16.8k
- Forks
- 1.2k
- Avg merge
- 1d 19m
- Merged PRs (30d)
- 9
Description
First of all, I would say thank you for your amazing job! I always wanted to profile my code and never find the Swiss Army knife for that (CPU / GPU / memory / performance per line of code).
I read the manual and look in the code of the master branch to understand the limitations/restrictions for macOS.
I would like to have your opinion about the following points to know if they can be improved/fixed:
TRACY_NO_EXIT/ Profiling is interrupted when the application exits : Is this a limitation in the macOS architecture or do you think it might have a workaround/improvement to fix this?- Crash handler not available: Is it because this is not a priority for you (due to the limitation below plus the problem with OpenGL which can be profiled), or is it for any other reason?
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
Review the manual and the master branch's macOS limitations, focusing first on TRACY_NO_EXIT and the unavailable crash handler. The issue names no specific files or tests; work would need to establish whether either limitation has a viable improvement and document a decided direction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, macos
- Domain
- operating-systems, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100