So, after the update I’ve launch Roblox Studio and login in and it says There was an error, please try again later.
So I’ve deleted roblox studio to download it again and now i can login but once in one of my map there ALWAYS something about the gui not showing so i just close roblox studio but when closing it only freeze. And even if I restart it does the same thing and when i try to click the play button it load but I have my character all gray and etc. (It happened to all the maps)
4 Likes
That might be due to your internet connexion so you should take a look at that.
If the UI is not loading make sure all the properties indicate it’s visible and if it’s ingame, then try preloading the UI.
2 Likes
This is what happen when i try to close the app of game
And this is what I see, I tried to restart my computer multiple time I tried to do everything I could thinkk of
Here is what happen everytimes since the update.
2 Likes
Just got a new PC and this has begun happening to me too. When closing a certain place file, Studio doesn’t close–just goes grey and freezes, and the memory consumption goes up and up with every second that passes by after that point. It’s important to note it only happens to a specific place file–others allow Studio to close just fine. So I’m assuming it’s something specific in the place that’s causing this freeze up.
When I’m working on this specific place that causes the freezing/crashing I now need to use Task Manager to manually exit out of Studio to avoid this from happening.
@butterthebig Think you could look into this? Let me know what info is needed and I’ll get it right over.
If you have a specific place to reproduce that issue we’ll take a look at it. You can DM it on the thread for this ticket Also DM a log file.
Just a hunch based off a similar sounding problem, can you turn off any betas? We had a similar locking issue with the new Luau type solver beta. If you turn it off and it doesn’t repro, we can send it to that team.
1 Like
You’re right—disabling the new Luau type solver fixed the issue.
But I dug deeper. After 3 hours of delving through my entire game’s codebase, I found the culprit to be a single ModuleScript:
AccelTween.rbxm (3.2 KB)
I really hope this helps, and that it’s somewhat of a quick fix considering I’ve isolated the issue to a tiny script.
Do you still need a log file even though I’ve narrowed it down this much? You might be able to repro yourself with this.
Let me know!
@Yuria_theWitch Maybe you’d be interested in taking a look into this? I know you’re on the team responsible, so worth a shot
A log file isn’t necessary. If that place file reproduces the issue, that is everything we’d need to investigate it. Thanks for your time and effort in reducing it so much!
1 Like
Just checking, did the below help with your issue?
Thank you for reporting this and providing a good reproduction! This kind of denial of service for autocompletion and the associated continuously increasing memory usage is unfortunately the current outcome of severe performance edge cases from type inference, which the New Type Solver is more prone to as we’re working through these issues. You can avoid the problem today by opting out of using the New Type Solver while we continue to work on these issues. In the interest of making our tickets manageable, I’m closing this as a duplicate of New Luau Type Solver - Type Solver Doesn't Activate.