My friend has been unable to reproduce this issue on their device yet I have received multiple reports from other users saying they are having the same issue. I have already attempted to disable any programs that may interfering with Roblox only to come to no luck. This has only been occurring since either the latest version (Release Notes for 581) or the version before that (Release Notes for 580)
Reproduction Steps: This does not reproduce on all devices
Open Roblox Studio, and remain open for at least 20 seconds
Close Roblox Studio
Open Task Manager and observe that Roblox is still reportedly actively using up RAM
If it helps the team, I’ve found a workaround, setting RobloxStudio to run in “Compatibility Mode” of any of the following makes the application run as expected:
Windows 7
Windows Vista (Service Pack 2)
Windows Vista
Windows Vista (Service Pack 1) Windows 8 does not work!
Setting the compatibility mode does however make program execution much slower and is therefore not a long-term solution
This issue is deeply affecting my Studio experience, I have to permanently have a task manager instance open to kill Studio once I close it, all because Studio can’t close itself. The workaround with compatibility increase load times for everything by 200%, this is a severe issue and altogether may make me stop Roblox development in the meantime since I simply can’t develop knowing my computer may have tons of dead Roblox Studio instances open that I’m unaware of…
Just to add extra context as well since I’ve finally worked out how much RAM is used:
(~300MB + place file RAM usage) is added to your RAM every time you close Studio, this a severe memory leak. To put it in scope, every time you close Studio on an affected machine (still unaware on what hardware / setup exactly causes this, although previous versions were unaffected), the RAM is kept in memory permanently and can only be freed via manually clearing RAM via task manager. This can outright lead to programs being forced closed (such as me, Studio RAM got too much to the point that explorer.exe quit, bricking my machine).
I thought I was going crazy not too long ago when a simple local server with 2 test accounts almost crashed my laptop. I’ve had to use task manager to keep cleaning up these RAM consuming monsters that are left behind. I had over 20 at once running without me knowing, which caused explorer to flicker a bunch and that’s when I opened task manager. How does a memory leak this bad even happen?
Nice to hear I’m not going crazy and others are also experiencing this! Yeah, this is severe in terms of memory leaks and honestly incredibly concerning how this passed internal QA.
For anyone who does have this issue (Roblox Studio uses 0% CPU yet still consumes RAM when closed) and is on Windows, use the following as a workaround, note that it will dramatically decrease performance:
Find the RobloxStudio.exe executable on your computer (you can find this by finding the source of the desktop-shortcut created on your computer)
Right click the exe and go to properties, then go to ‘Compatibility’ and select ‘Windows Vista (Service Pack 2)’ as the compatibility device. This is the most optimised compatability mode for Studio from my tests, you can experiment yourself if you wish, however do note that Windows 8 compatibility mode does not solve the bug.
Then go ahead and hit ‘Apply’ and relaunch, Studio will now run much slower than usual, yet you will no longer have the issue either. You may have to end the process of any running Studio instances in task manager too!
Hello - just to be sure we have the right log entry (the one attached indicates no shutdown was attempted, which isn’t surprising if the program is still hanging around), can you
ensure all instances of studio have been shutdown or killed
clear all logs from the log directory (or move them)
Rerun your test and resend log.
It could be that that’s all there is, just want to be doubly sure so we can track this down quickly.
In addition, can you note from your repro whether or not this occurs in any state of studio, or just the one you indicated in the report (i.e. you never left the start page). That will help narrow things down. So try shutting down on the start page, after opening a place, during play solo etc.
Also, can you be specific on how you exited studio, or if that matters (File->Exit, close button ,close place tab, etc).
Lastly, can you let us know what version of Windows you have installed?
I have added multiple new log files to the private message, all of which are retrieved via different methods of closing, the original log file I sent appears to have actually been incorrect likely due to the other “ghost” instances interfering the file so these logs appear to be more accurate, showing the application close via logs.
This issue occurs in all states of Studio, I simply listed the easiest way to run into the issue, if this issue is occurring on your machine, any method of closing in any state of the application makes the issue occur.
All methods of closing causes this issue, including File->Exit, close button, close place, and even using Task Manager to kill the subprocess! The only way this issue does not occur is if you kill the entire RobloxStudio process via Task Manager.
It is also worth noting that upon forcing the application to close via Task Manager, Roblox Studio uses ~4% of my CPU for a second before then shutting down so it does appear to be aware of the fact that it is open.
Update on this, for some strange reason, if you have one of these “Ghost” instances open and close the RobloxPlayer: RobloxStudio will launch, this is incredibly strange and entirely breaks the core concept of closing an application.
This still is an issue and is hindering my overall Roblox workflow, “ghost” Studio instances affect the Roblox player, forcing themselves to open a new Studio instance when the Player is closed and overall seemingly cause a poor Roblox player experience when open. Likely due to the fact that they hog RAM. I cannot be expected to be productive as a developer when I constantly need to have Task Manager open to force kill Roblox Studio.
Compatibility Mode causes major hiccups in rendering speed and overall is only just a workaround for severe cases. This bug needs to recieve high priority because a memory-leak as large as this one kills any chance of low-end machines being even able to develop on the platform, it is disastrous that this is still an issue.
17 days later and this is still an issue, it is incredibly agitating to use task manager to constantly close these instances and it is saddening that a solution has not been found yet.
Just wish to state that this is still occurring and that I have observed a bit more since the original report. Roblox Studio holds all “subprocess instances” within “processes”, from my observations the following occur upon launching a subprocess:
If a subprocess is the one to launch Studio (such as opening a different place via the asset manager, etc.): the new “sub-process” gets housed under the same “process” as the current “sub-process”, this makes it a nice “family tree” of Roblox places in where all related places are together.
If you launch Studio via any other method (website, launcher, etc.) a new process is spawned always, this means we must be very careful when doing this as multiple processes exist, making this bug much worse.
The reason why I mention this is because subprocesses are unaffected by this issue, only the processes themselves are affected
The issue however comes when I hit “close” on the Roblox Studio application (or alt+f4, etc, basically any way that you may close the application), this is how things seem to work if no other subprocesses are active under the current process (in order):
Process
Windows 8+
Windows 7 and below (compatibility mode)
Sub-process is killed
High CPU usage for a few seconds
CPU usage continues to fluctuate up and down for a few seconds
Hi, for anyone tracking this bug - the current workaround to avoid this issue is to disable Oculus if not needed, or shutdown studio from task manager. Something with Oculus is blocking studio from shutting down properly at a low level. We will investigate a permanent fix now that we know where the issue is. Shout out to Abcreator for helping us track this down!
