Skip to content

Tracy 0.13.1 + Fixed major memory issue#122

Open
RulHolos wants to merge 1 commit intoLegacy-LuaSTG-Engine:masterfrom
RulHolos:master
Open

Tracy 0.13.1 + Fixed major memory issue#122
RulHolos wants to merge 1 commit intoLegacy-LuaSTG-Engine:masterfrom
RulHolos:master

Conversation

@RulHolos
Copy link
Copy Markdown

@RulHolos RulHolos commented Mar 28, 2026

Tracy, by defaults, keeps the data of the traces it has since the engine's startup, so it can display them a long time after the engine started and still have all the infos. However, this introduced a major issue where, when calling tracy zones and other functions a lot of time, would lead to major increase in memory usage and memory leaks, eventually leading to a crash.

Even without enabling tracy link, the calls to the macro were still present in the code, leading to the same issue in debug and release versions of LuaSTG-Sub. This is a minor issue in normal gameplay, but when starting to play with worlds and other more intensive functions, it becomes a major issue. With testing a intensive game, we went up to more 5Gb+ memory usage.

Enabling the TRACY_ON_DEMAND compile definition in tracy.cmake fixes the issue.
I also took the opportunity to upgrade to tracy 0.13.1 which is more stable.

- Fixed a major memory leak issue that leads to crashes
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.

1 participant