Skip to content

Mitigate Tracy dep version woes #20109

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

liamaharon
Copy link

Objective

Turns out, Tracy dep (in)compatibilities can be a headache. Here was my experience following the Profiling Tracy documentation:

I ran into this error when I attempted to connect to my bevy client:

Screenshot 2025-07-13 at 14 39 27

Attempting to find where the version incompatibility stemmed, I found these tracy dep versions and a link to the compatibility table in the source:

# Tracy dependency compatibility table:
# https://github.com/nagisa/rust_tracy_client
tracing-tracy = { version = "0.11.4", optional = true }
tracy-client = { version = "0.18.0", optional = true }

This led me to believe I needed Tracy 0.11.1, to match the tracy-client version 0.18.0.

This was confusing because 0.11.1 is the version I already had installed (by running brew install tracy), and latest Tracy version currently available on brew.

It turned out that Cargo was eagerly pulling tracy-client 0.18.2 instead of 0.18.0, making the Tracy version I needed actually 0.12.2. At the time of writing, 0.12.2 is not published on brew.

Solution

I've pinned the Tracy deps, and mentioned in the comment which Tracy version Bevy is compatible with.

I've also added some notes to Profiling Tracy documentation to explain

  • How to determine which Tracy version to install
  • That MacOS users may need to compile from source if the required Tracy version is not available on brew.

Testing

  • Did you test these changes? If so, how?
    I ran Tracy locally.

  • Are there any parts that need more testing?
    I don't think so.

  • How can other people (reviewers) test your changes? Is there anything specific they need to know?
    Follow instructions to run Tracy

  • If relevant, what platforms did you test these changes on, and are there any important ones you can't test?
    Tested MacOS. I think change should be OS agnostic.

Copy link
Contributor

Welcome, new contributor!

Please make sure you've read our contributing guide and we look forward to reviewing your pull request shortly ✨

@alice-i-cecile alice-i-cecile added this to the 0.17 milestone Jul 13, 2025
@mockersf
Copy link
Member

I would prefer to not pin versions, the instructions you added to the profiling docs will pick the actual version anyway 👍

@liamaharon
Copy link
Author

I would prefer to not pin versions, the instructions you added to the profiling docs will pick the actual version anyway 👍

Sure, removed the pin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants