Roblox studio crash during place final loading step

Bug Reports Studio Bugs
,
1

During last month I did 3 reports about the same problem. After one of them I was told that type solver beta could do such, so I disabled it and everything was fine until today.

System info: (+ 8GB of RAM)
image

Š”Š½ŠøŠ¼Š¾Šŗ эŠŗрŠ°Š½Š° (1304)
Š”Š½ŠøŠ¼Š¾Šŗ эŠŗрŠ°Š½Š° (1304)1280Ɨ720 14.4 KB

0.675.1.6750723_20250603T185511Z_Studio_51DA9_last.log (244.9 KB)

attachment_0.675.1.6750723_20250603T185511Z_Studio_51DA9_last.log (176.3 KB)

1 Like
2

I see a few incidents from around when you submitted this that seem to point to editable mesh - can you double check the log is from loading that place? Also, assuming this is a specific place that is crashing?

Best case for resolving quickly is to DM us a minimal rblx that reproduces the problem. Possible that you have something in your save that is disagreeing with the latest code.

3

Yes, Iā€™m sure that the logs are from the loading place. Right at that moment when the bug happened in 22:05, I went to logs and grabbed last file + went to crashes logs and also got the latest file.

About the specific place, I have no idea as I donā€™t have any other place with such place size.

4

Additional observation: Few minutes ago I for the 2 second time today tried to load that place. Everything was Ā± good, place wasnā€™t freezed, I could move my camera around but still there was no textures and lightning loaded. However, right at the moment when I clicked the arrow to expand the ā€œChatā€ folder in explorer, studio immediately crashed with same message ā€œTeam create backup file savedā€

5

Hi, we looked at this and were able to replicate the behavior using your place with the New Type Solver Beta enabled. Without it on, it loaded fine every time. Is it in any way possible this is still enabled? In some cases, betas may be forced on by teams (I donā€™t think this has happend) but there are a couple other known issues:

  • Weā€™ve seen some settings reset for users that have Windows account names with non-ASCII characters in them (fix coming soon)
  • Weā€™ve seen some issues where betas can be confused by multiple Roblox accounts in Studio - its possible to have a beta enabled on one account, switch to another account and have the beta still enabled but not shown as enabled. ( Still working on the fix)

So I would first make sure that the beta is really really off - if you switch accounts, make sure its off on every one. (FWIW I donā€™t see it in the log, but could have just been that run)

If you still are having a problem, then I think weā€™re getting into some murkier areas. You could try turning off betas and seeing if something else is getting in the way, but New Type Solver was the only one we found to cause errors on loading.

After that weā€™re looking at a HW issue - after loading on Windows I saw ~17, 18GB working set on the process. That climbed to 24GB when I ran it. At that point, on an 8GB machine youā€™re already at +200% just from Studio on installed RAM. Thatā€™s not including any other things that are running, and doesn;'t include the memory the OS is going to take. So a large majority of the process RAM is paged at that point, which is going to hang the system a lot. In the cases when it does load, how long does it normally take? Thereā€™s not a lot of action we can do on our end, but generally if youā€™re in this situation with a place this large its going to be a tough experience on a machine which is underpowered for it.

If this is the type solver, I can forward onto that team and have them look specifically at your place for diagnosis - likely some unique script thatā€™s causing it to hang they havenā€™t accounted for yet.

6

Alr so, let me answer everything in order:

  • On may 7 you told me about type solver and that it could do such things to my studio. On may 8 I disabled it and everything was working perfectly. Studio was taking like 10-15 minutes to load fully with all textures, lights, meshes and etc. (which is actually very good for me) there was no crashes and no lags inside the studio. All this positivity lasted until June 3 when I posted my last report for now about same problem appeared again (as I remember, on this day there was new roblox update with new explorer UI or smt like that, I donā€™t remember exactly). On June 3 I surely had my type solver disabled but there was still lots of beta features enabled. Then, on June 4 I went to studio, disabled most of the beta features. I left Dragger QqL Improvements and Import Queue enabled and after this I opened my place to check if this could help, and sadly It didnā€™t.
  • If weā€™re talking about the time which takes to open studio right now when this annoying glitch exists, it will be 20-30 minutes. After this time, no matter what I do and what I donā€™t do, it crashes with same error ā€œTeam create backup file saved.ā€

Note: As I said before, in the period of time from may 7 till june 3 (Maybe the update and the issue happened before the june 3 but still) everything was working as intended and my low amount of RAM did not affet studio functionality and place loading processes.

P.S.
Iā€™m fully okay with waiting time for the studio to load and fully okay with some freezes and lags inside it, but fact that Iā€™m wasting 30 minutes of my life with hope that place will open and at end I see a crash and error message does really disappoint and demotivate me.

7

And yes, forgot to mention. Before I had my windows account name in cyrylica which probably falls under Non-ASCII. I changed it right now to English characters and will try to test it out.

8

I doubt those last two betas are the issue but you could turn those off and see. I didnā€™t see any extra plugins installed but worth taking those out as well.

I guess we didnā€™t look at the Team Create angle before - can you load the file you sent me ok? Just under Team Create this fails?

9

Yes, I also deleted all plugins which I had as I thought that they could also be the issue.

About the place load, I could do it only on the week, so I will let you know about the results.