What am I supposed to press to continue debugging, with FFlagDebugLuauDeferredConstraintResolution? #1192
-
|
When I get this What am I supposed to press, to re-enable the autocomplete and get rid of the orange line, without having to restart Studio? I think I am using the Debug thing wrong, because I get get beyond this orange line step whenever I trigger it. Unless it means that it crashed? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 7 replies
-
|
Once an internal compiler error has been triggered, type checking is disabled for that Roblox Studio instance. There is no way to recover from that state beyond restarting Studio. This is deliberate - that category of error is triggered when Luau detects that something has gone wrong beyond recovery and Luau's internal state may be corrupted. In order to avoid crashing the entire Studio instance (and potentially losing data), we disable type-checking for that instance from that point on. With that said: that error is unambiguously a bug, and you should file an issue for any code snippet that causes one. |
Beta Was this translation helpful? Give feedback.
-
|
Sounds good, but how do I describe the bug. Is there a way for me to view logs, will it be in the log files? |
Beta Was this translation helpful? Give feedback.
-
|
It may be printed to the log output, but just knowing the error message isn't terribly useful without a code snippet to reproduce this. If the code in the screenshot above triggers it, that's worth submitting on its own, without logs. |
Beta Was this translation helpful? Give feedback.
-
|
I was more thinking about avoiding duplicates in the bug report, because if I don't have a way to name it I wouldn't be able to check if this issue already exists. There was also a Roblox Studio Crash that occured on one of the code, so I have 3 in total to submit I think. I'll look forward doing that shortly. I am more interested in this topic #1193 (reply in thread) |
Beta Was this translation helpful? Give feedback.
-
|
if it's supposed to show in the output log, it may didn't show for me, which fast flag do I need for the logs? |
Beta Was this translation helpful? Give feedback.
-
|
So is this a compile error?
won't I get the same here? |
Beta Was this translation helpful? Give feedback.
-
I submitted it with the screenshot as proof along with the code snippet and the location, but it was closed because of the screenshot.
Do I have to report all 3 issues on the Developer Forum now? There's 2 that trigger the debugger and one that crashes Studio without triggering the debugger, but the Debugger FFlag was used. |
Beta Was this translation helpful? Give feedback.
-
|
If this is related to the runtime debugger that should be reported on the Developer Forum. |
Beta Was this translation helpful? Give feedback.
-
|
uhhh, well the script never ran, it's purely the autocomplete or lexer or something |
Beta Was this translation helpful? Give feedback.
Once an internal compiler error has been triggered, type checking is disabled for that Roblox Studio instance. There is no way to recover from that state beyond restarting Studio. This is deliberate - that category of error is triggered when Luau detects that something has gone wrong beyond recovery and Luau's internal state may be corrupted. In order to avoid crashing the entire Studio instance (and potentially losing data), we disable type-checking for that instance from that point on.
With that said: that error is unambiguously a bug, and you should file an issue for any code snippet that causes one.