Studio randomly crashes after some time

Hello, so I’m getting this error after having it open for some time. Nothing was plugged in or out the computer when it happened.

System Info:

  • Windows 11, 24H2
  • Studio Version 0.695.488.6951050 (64bit)

Enabled Betas:

  • Acoustic Simulation
  • Assistant Mesh Generation
  • Avatar Joint Upgrade
  • Dragger QoL Improvements
  • glTF Export
  • Improved Constraint Tool
  • Improved Find all/Replace All
  • Improved UIStrokes
  • In-Experience Avatar Auto Setup
  • Live Animation Creator
  • New Luau type solver
  • New Studio Camera Controls
  • New Video API
  • Next Gen Studio Preview
  • Proximity Prompt Indicators
  • Revamped Asset Manager
  • Script Sync [Early Preview]
  • Texture Generator
  • UIDragDectectors
  • Video Uploads

A private message is associated with this bug report

5 Likes

Most crashes are caused by the new Luau Type Solver, disable it to fix the problem

2 Likes

It’s not that, I didn’t open any script in the session where I crashed. Only modified UIs

1 Like

Even if you don’t have any scripts open, it’s running in the background and this beta has a memory leak, if I’m not mistaken

1 Like

Are your graphics drivers up to date?
Can you list your graphics card (incl. the integrated one if present)?

My GPU driver was one version behind, last update 5 days ago (14/10)

Here’s my full specs
CPU: Ryzen 7 9800X3D
iGPU: AMD Radeon™ Graphics
GPU: RTX 5080
RAM: 64GB DDR5

EDIT: Updating the driver with studio open gave almost the same error, but one off: 0x887a0005 instead of 0x887a0006 from my original message

Updating the driver with studio open gave almost the same error

This is normal behavior. The driver for your graphics card has to be stopped and started, studio uses this driver, hence it crashes.

But I pretty much started having those since I started using the “Next Gen” studio.. not sure how linked one and the other is

Correct on the above post that upgrading the driver while running will result in a device removed error. The error you’re seeing the rest of the time is the GPU being hung, which indicates the device failed to respond due to something crashing. Given the HW I wouldn’t assume this is a resource error or something given that you have plenty of VRAM/RAM – unless you’re seeing this after going to other applications and coming back (maybe playing a game or something). Even then that’s not going to be normal. Upgrading the drivers is a good first step, have you noticed any difference in frequency of the crash on this? Have you made any other changes GPU related to the machine (new setitngs, installed the GPU recently, new utilities, etc?).

Most of the time these types of issues are outside our control and are driver/HW related, but it can be possible under specific conditions the renderer is issuing bad instructions. We haven’t seen any increase in error rates since rolling out Next Gen to most people, but you can try disabling and see if that helps at all. Also, is there anything else like a specific place that this occurs on that might help narrow down a specific case where this breaks?

1 Like

It happened both times when I had studio in the background and doing other things, the other applications kept running without issues

That could be something. I know I often have tons of applications opened. I tried opening studio + the game I’ve been playing in the last couple days and I have 13/16GB VRAM usage (which is somewhat close to the limit).

But with my older GPU (8GB VRAM), the only problem with studio was opening it while another VRAM-expensive game/program was running. If I was at or too close to the 8GB, studio would simply shutdown during startup. Opening it before the expensive game/program would work as intended with no errors and in rare cases close with no errors (that was maybe like 6+ months ago? with the new GPU I’ve never had that problem because I have plenty of VRAM)

Since the crash happens somewhat rarely, I’ll try to see in the next couple days when it crashes, what I was doing and the resources usage (studio stays opened until I press “OK”, hopefully the resources are not dumped until then). If I find a semi-reliable way to reproduce the crash, I’ll try with the old studio

I haven’t made any changes on the machine that I can remember and for the GPU I haven’t changed any settings before/since it started happening (except upgrading the driver 2 days ago)

Both times I saw this happen it was in different places, so I don’t think it’s related to a specific place
(One of those places bring studio up to ~4GB memory usage while the other one only bring it up to ~1.5GB)

Hello,

So this happened again. I had 2 studio instance opened, both crashed with couple minutes interval.

I wasn’t on studio when it happened, it was in the background. One of them was a different place from the ones from before

I’ll attach the logs for each studio crash to the private messages, hopefully it can help more

Thanks - looking at these as well and the context helps too – while Studio was in the background, what applications were taking foreground resources? Gaming? Chrome? 3d editor?

I think in the foreground i only had Vscode and an instance of Firefox watching videos.

In the background is another story:

  • Couple more instances of FF (4-5 windows with ~5-10 tabs each)
  • War Thunder
  • Discord
  • paintdotnet
  • and likely some other applications, but I can’t remember 100%

If it happen again, I’ll note down every app I had opened and whether they were in fore/background