Studio will stop working when stopping play solo without resuming from breakpoint error (Sometimes crashes)

Bug Reports Studio Bugs
#1

Bug

Basically, when play testing (Run or Play) in Roblox Studio, you encounter an error that
causes a break point in code and you don’t click resume before ending that play test session, Publishing, code formatting and Command line code will not work, the temporary solution I have to this is that you can just save the game to your drive, but this doesn’t necessarily bring back all of the features that have been broken. The only way I can see this happening is if I forget to resume play after a break point error has occurred. Any more info that you need, don’t hesitate to ask.

Where the bug happens

Play testing

When it started happening

I forget exactly when, but I believe it was 1 or 2 updates after the expressive output window was released for beta

Screenshots

Publishing will infinitely do this when attempting to close studio (When you save to disk or manually crash studio with task manager)
image
View of the file menu publish buttons being softlocked
image

RemoteInstances and BindableInstances will not register Fire and Invoke requests

image
image764×72 3.59 KB

These events should output this:

true
78

Recent log file

The log was removed from the repo

4 Likes
#2

Hi 0x6e7367,

When you say “break point”, are you setting a breakpoint on a line of code within a script or are you referring to a point in time where your game breaks? Either way, can you provide a script that causes this bug to occur so we can try to reproduce on our end?

#3

By breakpoint, I mean an error that is level 0, it pauses the session

2 Likes
#4

I could reproduce this by stopping the simulation while the debugger was sitting on a breakpoint. Just insert a script, put a breakpoint on print("hello world"), run the simulation, and stop it once it breaks. The most obvious symptom is that camera control in the edit mode viewport no longer works (e.g. right click drag to rotate the camera is broken). No errors in output.

1 Like
#5

Hi PeZsmistic,

Thanks for those instructions, although I feel I am still missing something as I’m not able to reproduce. Here’s what I’m doing:

  1. Open a new Baseplate
  2. Add a script
  3. Put a breakpoint on Hello world print statement
  4. Playtest using Run
  5. Breakpoint is hit, click Stop

After completing the above, I do not see any effect to my camera control in the edit mode viewport and have no issues publishing.

#6

Can you try by using play solo (with your character)? I did not test this simply using Run. I don’t recall my beta features (at work right now) but I do have a fair few of them enabled.

#7

I tried all playtest modes (Play, Play Here, Run), I get the same results as described in my post above

#8

I will see if I can identify anything unique about my setup that causes this when I am home later tonight. I did reproduce the camera issue this morning though.

You might want to try enabling a ton of beta features in the meantime and see if any of them cause this.

#9

Ah, finally seeing this now, just need to narrow down what Beta Feature(s) causing this, thanks PeZsmistic

0x6e7367 thanks for the report, we will look into this

2 Likes
#10

FYI: This seems to be impacted by the Plugin Debugging beta feature, we will look into the cause but if this beta feature is disabled you should not see the bug. Please let me know if you see otherwise, thanks

#11

@tamtamchu
Breakpoints, errors, anything that causes runtime to pause will be suitable to reproduce the bug

1 Like