I’ve been encountering a frequent studio crash and there seems to be a correlation with breakpointing while debugging my scripts. When Studio crashes I have to completely reopen the application, reopen the experience, and then pick back up from where I left off.
I’ve noticed upon restarting studio the breakpoint at which studio will crash is often different.
Not sure if this is a memory limit issue, but it does appear I have some available ram when I crash.
The experience that I’ve noticed this issue in is large, many high quality models, and many scripts. However about a month ago this same experience was running smooth without frequent crashes.
In other experiences I don’t notice the crash so much.
I have also noticed studio crashes periodically when left open for too long.
I have also noticed it feels like it’s crashing more frequently when in a team create session.
Steps to Reproduce:
Open a large project in Roblox Studio.
Place a reachable breakpoint
Start the game in Play mode or run the script.
The studio crashes somewhat around the time after the breakpoint is hit
Frequency:
Seems to be at least 2 times per hour, and upwards of 4-5 times per hour.
This issue has been happening to me as well. Sometimes, I can’t even open the studio without it crashing instantly, which is consistent with one of my places. I’ve noticed that it tends to freeze and crash when I’m debugging using breakpoints as well. This seems to have recently started happening, as I’ve otherwise had no issues in the last few months.
This same issue is occurring on my studio instances as well. I receive no logs or indications that the instance is crashing; it just disappears. This started happening earlier this week and has been consistently occurring since then.
I am having similar problems with Studio crashing or freezing. When i work on something like moving a part or something similar. The studio window freezes.
Hi, can I get a log (you can DM me) that follows any crash? Even if it doesn’t mention a crash specifically there still might be some clues we can use. In addition, if you do have a 100% crash case, its most beneficial to help us reproduce this - could be HW specific (harder), plugins installed, or place specific. In the case of a place, getting to a minimal reproducible case that we can then use on our end is the most helpful. We have a known such issue just discovered a couple days ago of a datamodel that had an extremely deep datamodel tree (400+ levels) that was causing a bad interaction with some recent fixes. We’re patching that now. If you can take a look (which I know is harder with sporadic crashes) on different places, blank baseplate template, etc that will help us narrow down what’s going on. But logs are helpful regardless!
Can you please update Studio to the latest version (at the moment it is version 0.640.1.6400735) and give it a try?
We added a fix to the other issue described above in this release and are interested to see if that fixes issue mentioned in this thread as well.
(Please note this fix will only get applied onto Studio sessions that are started after this point of time from the version no earlier than 0.640.1.6400735)
If the problem still persist, would appreciate the log for that particular session as well as a valid minimum repro place/asset/steps that we could test internally.
I’m using latest version today 0.640.1.6400735 and I was still experiencing crashes. My teammates were also experiencing frequent crashes as well. It feels like sometimes we have no crashes for an hour and other times we have like several crashes in a single hour.
In terms of consistency, I cannot pinpoint exact reproduction steps it really feels like I’m hitting a memory limit and that’s when it crashes. Sometimes I’m doing nothing, not even playtesting, looking at a different application and then I go back to studio and it’s crashed.
I have noticed:
When we have 4+ users in a team create session it seems like we all crash like once every 5 minutes
In solo team create sessions I crash way less often (but it still happens)
When using a MacBook Pro M2 studio crashes more frequently than on a Windows Desktop Gaming Rig
I can reach a crash even faster while debugging code
We were able to locate one of the crash dump based on the log you provided.
It is not the one we were chasing after (the one mentioned in the previous replies). I created an internal bug report and will ping corresponding team to help take a look. I (or some one from the other team) can keep you updated once there is progress on that one!
In the meantime, if you have more logs for the crashes that you would like to share, I am more than happen to look in the system to see if they are all related or not.
The internal JIRA showed In Progress on that ticket but I haven’t seen a PR being associated to that ticket yet. So I guess the engineer is still investigating / working on it at the moment.
