Just started a session and immediately crashed.
DxDiag.rbxl (it’s a .txt)
4 Likes
I’ll posts my specs too I suppose to see if that’ll help isolate the issue for the engineers.
DxDiag.rbxl (68.7 KB)
1 Like
Got this issue too since today. Also getting a bunch of freezes.
R7 1800X/1080ti/win 10
1 Like
Both of you have 1080 Tis…anyone else here have a 1080 Ti that can weigh their side?
1 Like
o/
I’ll test this tomorrow.
2 Likes
Relevant?
Im very curious if its the same problem as me.
1 Like
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
- yes? (not sure what you mean by same studio session)
- no (except for the terrain one but thats built in (i think))
- 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
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: Microsoft OneDrive
1 Like
Are you using a high DPI monitor?
1 Like
I’ve got an Acer Predator x34 (3440x1440), scaling set to 100%.
Dxdiag logs: https://pastebin.com/LAFYfeyP
1 Like
I’m also having tons of lag, which is making developing nearly impossible to do.
3 Likes
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
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
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
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.
1 Like
Been having these problems all day as well. Glad to know I’m not the only one.
2 Likes
I get my properties or explorer windows’ responses stopped, a temporary fix for that is changing desktop or restarting Studio.
What I mean by ‘responses stopped’:
Step 1: Select a random object, for me it was the sound in the explorer.
Step 2: Do some changes in it.
Step 3: Attempt deselect.
Step 4: Properties still shows the properties of the sound object in explorer and the selection in the explorer tends to be unchanged when selecting something else.
There are multiple ways to do it, but I didn’t really observe it carefully when the properties suddenly froze on me.
This problem happens inconsistently. I believe it comes from other programs running in the background first.
Test 1: Without any programs in the background.
Result: Respond hacks up a bit then proceeds.
Side Note: This test was inconsistent, sometimes it freezes until actions were done.
Test 2: With a few programs in the background.
Result: Respond freezes, unfrozen by a few seconds.
Side Note: This test was inconsistent, sometimes it freezes until actions were done.
Test 3: My usual preference of amount of programs in the background.
Result: Respond freezes, only unfrozen upon change on desktop or window.
Side Note: This test was inconsistent, sometimes it freezes until actions were done.
In conclusion: There’s something freezing a few windows in the Studio; causes crashes a bit more frequent.
Further Information Request: What do you have in the Workspace?
Another test needs to be done this way:
• Edit in an empty baseplate.
• Edit(s) in a workspace with only certain elements.
• Edit in a functional game.
Information Needed: How long does it take before crash? If it all goes beyond 10 minutes or crashes exists in all objects inserted, then it can be analyzed as inconclusive.
TL;DR - Test the Studio by experimenting with certain objects in the game; I don’t have a problem with this except properties freezing on me.
2 Likes
This is happening to me aswell, I’m in the script editor and attempt to select something on the explorer, doesn’t work at all, just a long freeze, if I try to open another script while having one open (and maximized) it doesn’t work at all. If I “minimize” the scripts open I can select anything in the explorer just fine, same goes for closing all of them. This usually starts happening 10~ minutes after the place was opened which makes it so I have to restart studio every 10 minutes.
1 Like