When repetitively opening and closing the menu in a game, it causes a very slight memory leak which can build up to be more substantial over time. (Please reference Repetitively opening menu causes memory leak specifically in Enum.DeveloperMemoryTag.Gui - #4 by MrJake092209 aswell)
System information: 11th Gen Intel(R) Core™ i7-1165G7 @ 2.80GHz, 16.0 GB, Intel(R) Iris(R) Xe Graphics
Here is an example of the Roblox menu being repetitively opened and closed; notice that the memory tag for Gui gradually increases from around 4 up to 6:
After doing this for a little longer, I was able to jump it all the way up to 7:
Game place used to visualize memory (among other things):
Datapoints.rbxl (76.5 KB)
Expected behavior
I expect either the memory to decrease back to its original level after a while or for the memory leak to not occur at all.
A private message is associated with this bug report
6 Likes
Interesting find, I wonder if there are other CoreScripts or Roblox features with memory leaks too like the Hamburger menu or the chat. They have horrible performance just like the menu.
1 Like
There have been other bug reports including memory issues with coreguis and even after months those have yet to be fixed
1 Like
It’s also even worse with the report ui:
The memory leaks and inefficiency of the current coregui menu simply cannot be made ignored anymore. These are pretty glaring issues with the current ui, and they either need a fix or a complete rewrite.
2 Likes
honestly i wouldn’t be surprised if all the features associated with the topbar have memory leak potential
interestingly enough, the topbar also appears to have some kind of “waiting for load” thing that’s got the potential of infinitely yielding, something which i feel like wasn’t there before with the old one, which might be saying something about the codebase of the client
Now if anyone wants to try it with all the other topbar things (music, self view, party etc.) and compare frametime/memory usage then that’d be a decent way to know just how terrible the topbar both looks and functions
2 Likes
Adding onto this,
This is a very common warning, that is internal to Roblox. Take into factor
Almost every error occurring in my place is Roblox related. (blurred some stuff out because I can)
2 Likes
This can happen when, at the beginning of loading the game, the loading process freezes for longer than 5 seconds, which causes the warn, The code can be found in ExtraContent, corescripts, etc:
This warning could very well be fixed by setting a timeout as the second argument to WaitForChild, but I guess they just don’t want to do that or something.
1 Like
For “Failed to set UISizeConstraint’s MaxSize as it is smaller than MinSize”, an easy way to replicate it is to simply enable DevConsole (in a real game there would likely be way more guis that can result in the same thing) and convert the screen from being maximized to being a tiny window on the screen:
Again, can happen with other UIs. This notification is mostly served as advice to actual Roblox devs (who ALSO have yet to fix this bug report!!!) as to why it happens (or atleast one cause of it). And also to discourage the warning from occurring in the first place.
1 Like
I don’t understand why no Roblox engineer has left a message yet to say that the ticket is in the backlog, because honestly memory leaks should be a priority (along with other performance bugs).
The worst part is that this memory leak is very easy to reproduce, you just need to open the menu…
1 Like
If that wasn’t bad enough, the entire client is a memory leak, as seen in this post Unreasonbly high RAM usage on roblox mobile client
It’s so bad, it pretty much requires inventing new terms as the memory leak seemingly also transcends to CPU and GPU frametimes
It’s extremely disappointing to see anything performance related be silently blacklisted from being reviewed or whatever this no-show nonsense is
While memory leaks shouldn’t be as high priority as a vulnerability, it should still be resolved with relative urgency
I’ve recently played bee swarm simulator and noticed many more framedrops after the migration, so I don’t just want a random (but still significant and constantly occuring) memory leak to be fixed, I want all the performance issues to be resolved
3 Likes
