Getting lots of studio crashes - extremely difficult to develop

Bug Reports Studio Bugs
#1

Since today, me and several others have been getting lots of crashes as we use studio. Key takeaways:

  • Properties and explorer windows get progressively slower to respond as time goes on
  • Eventually performing an action with one of those windows will cause roblox to crash

I haven’t been able to make a session last more than 10 minutes.

14 Likes
#2

What are your specs? I’m not getting any of these issues.

1 Like
#3

I’ve been having this too, been working on plugins most of the day.

My workflow has just been editing a plugin then saving it locally to test. Rinse and repeat.

After a handful of local saves performance starts to take a dip and eventually I get a crash.

2 Likes
#4

Just started a session and immediately crashed.

image
image

DxDiag.rbxl (it’s a .txt)

4 Likes
#5

I’ll posts my specs too I suppose to see if that’ll help isolate the issue for the engineers.

image

image
image471×501 17.2 KB

DxDiag.rbxl (68.7 KB)

1 Like
#6

Got this issue too since today. Also getting a bunch of freezes.

R7 1800X/1080ti/win 10

1 Like
#7

Both of you have 1080 Tis…anyone else here have a 1080 Ti that can weigh their side?

1 Like
#8

o/

image

I’ll test this tomorrow.

2 Likes
#9

Relevant?

Im very curious if its the same problem as me.

1 Like
#10

For anybody experiencing this issue, it would be useful to know the answers to the following questions.

  • Does the problem persist if you close the active place and reopen it in the same studio session?
  • Do you have any plugins which use widgets installed?
  • Are you finding this occurs with a specific type of input? (mouse, keyboard, etc…)
1 Like
#11
  1. yes? (not sure what you mean by same studio session)
  2. no (except for the terrain one but thats built in (i think))
  3. for me it can happen with anything, Changing the name of an object, importing an object, moving the camera, it can be anything at all (even not doing anything sometimes crashes)
2 Likes
#12

Was pressing the enter key in a modulescript I was editing and it crashed.

Said something about 'AutocompleteException: syntax error: [string “”]:1: unexpected symbol near ‘.’.

Logs/dump: https://1drv.ms/f/s!AuhaHEzOBW_qgtoycJ2TjfJGogfX1w

1 Like
#13

Are you using a high DPI monitor?

1 Like
#14

I’ve got an Acer Predator x34 (3440x1440), scaling set to 100%.
Dxdiag logs: https://pastebin.com/LAFYfeyP

1 Like
#15

snip
snip1390×719 284 KB

I’m having lag while my scripts are open and I select something

2 Likes
#16

I’m also having tons of lag, which is making developing nearly impossible to do.

3 Likes
#17

I’m getting the same exact issue. It started the same exact time that widgets were enabled.

Glad to know it’s not me.

Hopefully they fix this soon, It’s directly interfering with my development.

1 Like
#18

I’m pretty sure it’s the newly added widgets. It only started occuring as soon as they added in widgets to studio.

Everyone does, the default terrain plugin / “widget”.

2 Likes
#19

I’m having no lag but the occasional crash, it is getting annoying though.
I had no problems yesterday using PluginGui, it was only until terrain plugin was updated. Don’t take my word for it.

1 Like
#20

Always used to see a slow increase in lag when selecting instances the longer Studio has been open, but it is now much worse and happens much faster.

Memory usage doesn’t increase, but Studio’s CPU usage cranks as high as it’s allowed to go for a moment every time I try to select an instance. If I continuously switch between instances it stays at the same high level of CPU usage. It’s much worse when the script editor is open instead of the viewport.

image

1 Like