Debugger Bug...?

I opened studio, pressed Play Solo on an empty Baseplate, and it works just fine.
however, when i go into a certain game I made, press Play Solo, it says:

“Debugger can be attached to a script or a modeule script”

I click “OK”, yet it won’t load. It is stuck in a loading screen forever, and I have to force close it.
I have not tried redownloading it yet, but I don’t think thats the problem :shocked:

1 Like

We can’t really do much without seeing the game. Any chance you could link to it? You don’t have to make it un-locked.

This has been happening to me as well when I try to play solo or start a server test in my game:

I’ve also tried testing in another uncopylocked game and got the same result:

Pressing f6 to start a solo test works just fine, though…

Edit: This popup occurs if you have any suggestions (Blue waves) from the script analysis.
Just having a script in workspace or serverscriptservice with:

print(Game)

will cause this popup.

I tried both, your game and the uncopylocked place and I am not having this issue.

What kind of computer are you using? Do you have any plugins installed? When did this start happening?

I have this issue too. Can’t play solo because this pops up then it forever loads until I kill the process.

As for my build,
Windows 7 (professional if that matters)
Using a GTX 670 graphics card
i7 3770k processor

I don’t know what sort of information to provide…I could list all my components but those would likely not matter.

When did this start happening?

After an update on Wednesday I believe.
I retried after removing my plugins and restarting roblox and this still happened.

System:
Windows 8.1
Processor: AMD A8-5500 APU
Radeon™ HD Graphics 3.20 GHz

This is happening to me too.
To me it occurs upon the second time I press run, often after I have entered a script, edited, closed the script and pressed play. It started happening after I updated my studio today (probably the wednesday-update coming later for me).

I run
O/S: Windows 8.1,
Processor: Intel i7-4700HQ 2.40 GHz
GPU: Nvidia GeForce GTX 870M

I agree with mark it started around wednesday.
I run
O/S Windows 8.1
Processor Intel i7 -[cant remember details]
but its a laptop with 8GB of ram, so its a terrible laptop.

8GB ram should be fine enough. Is it possible that it started happening on Tuesday? We had some features patch in around that time. Let me take a look.

The popup has stopped appearing now :smiley:

Edit: It just started happening again >;c

still having that issue, but now its every time I press Play or Play Solo (but not play server)

This issue is appearing for me as well now, it’s odd that it just randomly started happening in a game that I’ve had open for a while, and have been editing

Edit: Fixed, no longer caused by script analysis in ServerScriptService from what I can tell, but it did happen to me because I had some models with scripts in them in ServerStorage with the script analysis lines under one or two variables. After moving those to Lighting I was able to Play Solo again.

I hate to bring up old threads, but this still happens to me.

I found out what caused it though, did some experimenting, and turns out if I turn on FE and add a script in workspace, then press Play Solo, the “Debugger Bug” shows up. I made a place on it, although its easy to reproduce for me. Open up baseplate, turn on FE, add script in workspace = break.

heres the place for it:

although its fairly simple. like, really really simple, but really annoying to test with.

This also happens to me. 3 times yesterday. No details currently because I’m on mobile.

I am getting this also