Running game:GetObjects() within the command bar with an invalid content URL causes Studio to freeze/ hang (leading to a crash after input) rather than output an error, without this knowledge some developers can potentially lose game progress due to the abrupt shutdown.
Typed code within command bar:
Following any input after executing the above code, Studio hangs
Running game:GetObjects() passing any string (consisting of a number) at all even within a protected call will instantly crash Studio, this is 100% reproducible.
Sample code to be ran within the command bar:
The date this started occurring is not known.
I agree with this, this confused me a lot until I found out I need to add rbxassetid://
Instead of freezing maybe studio should show a error instead.
Thanks for the report! We’ve filed a ticket to our internal database and we’ll follow up when we have an update for you.
I am in the process of checking over bug reports and following up on some bugs that haven’t received any activity in a while.
Is this issue still occurring or can you confirm that this bug has been resolved? We are having a hard time reproducing this issue
I’m not really sure why it’s difficult reproducing this since I can, even after half a year following just the 1 line of code in the reproduction section of my post reproduce the issue a theoretically infinite amount of times passing any string containing a number:
To further clarify in case I’ve left anything blurry still here’s examples of usage with input that will cause Studio to freeze:
Now that I’ve tested again, I’ve noticed it takes some action (e.g attempting to move the camera, select random options etc.) sometimes after running the code to see Studio frozen. Usually the effect is noticed instantly otherwise.
To be perfectly candid I was kind of expecting a fix half a year later and not a confirmation of whether this still occurs. I understand this given how many bug reports Roblox receives though.
Hey Hippie, I can reproduce this 100% of the time with the examples above as well, you might want to ask the engineer to have a closer look at this one.
They were able to reproduce this issue as well. When there is an update from engineering i will pass on the info.
This still hasn’t been fixed, any updates?
Apologies for the lack of a resolution to this bug report, it looks like this one may have gotten lost in the backlog. I happened to run into this bug myself this week and I was able to find the root cause.
I’ve submitted a fixed this bug, the fix should be released next week all going well.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.