I was reviewing a large module script with a table that is nearly 5000 lines long. Upon opening the script I was greeted with this message. (note this popped up RIGHT when I opened the script, sorry for quality)
Sorry to hear you’re running into this. This is probably the new Luau type solver causing this issue. If you’re able to share a reproduction to help us narrow down the problem and fix the root cause, that would be appreciated.
I noticed this is only happening in a certain place file, turning off the new luau type solver did resolve it. I will send the place file shortly (simply opening it causes it for me)
Hello, I am also experiencing a similar issue, which I have proven to be the Luau type solver. I have experienced this issue with 2 systems. Turning on/off Luau was tested on System 1.
When the Luau type solver is turned off, my memory consumption is steady at 5-7gb. The game i’m opening is large. I experience some lag but no extreme lag.
When I turn the Luau type solver on, and the game begins to re-open, memory consumption skyrockets right through 5-7gb all the way to a peak of about 9gb of memory consumption. After enduring this for a small period of time, it seems my PC/GPU quits and everything breaks. Windows (apps) don’t load anymore, it’s like my GPU just gave up.
This does not occur on smaller games. The game that I experience these studio crash issues with is this game. I do have a plethora of other beta features enabled, however I have been enabling/disabling the Luau type solver after finding this post to confirm that the issue stems from this beta feature.
System 1 - PC: Windows 11 x64
NVIDIA RTX 2080 SUPER - 8gb VRAM
16gb RAM
Intel i7-10700F (10th gen)
System 2 - Laptop: Windows 11 x64
NVIDIA RTX 2080 SUPER
16gb RAM
Intel CPU (forgot specifics)
Imagery - Without Luau Type Solver:
Loading in - Less than a minute after startup
Loaded in - Waited 2 minutes, all stable, Workspace open
Imagery - With Luau Type Solver:
Loading in - Less than 1min
Peak recorded stats (could it have gone higher?):
I taskkilled studio after ~30 seconds of observation to avoid a full crash. I can also observe that CPU usage is elevated with the Luau type solver enabled. It should also be noted that I only moved around slightly and did not open anything, with no scripts open on the bar, during the Luau enabled test.
I taskkilled studio after ~30 seconds of observation to avoid a full crash. I can also observe that CPU usage is elevated with the Luau type solver enabled. It should also be noted that I only moved around slightly and did not open anything, with no scripts open on the bar, during the Luau enabled test.
Yes, that would be the “initial” type check that occurs when you open up your place file. The place files, or a reproduction if it’s a single script, would be very appreciated to help debug the root cause here! We’ve managed to hunt down a few of these nasty memory bugs, but they can be difficult to diagnose from afar.
Hello! Would you be able to try out the New Luau Type Solver beta again? We recently landed a performance fix that should mean Studio doesn’t use an unbounded amount of memory like this.
