Roblox client process carries on in background when closed after crash


#1

Whenever you crash and then close Roblox, the game client still remains ongoing in the background. You can check this by opening up task manager and seeing it under Background processes. The only way to fully stop it is by ending the task from the task manager, or waiting around one minute until it stops by itself.

This is annoying because if there was music going on while you crashed, you’ll continue to hear that music until the process ends. It’s also annoying because if you try to join another game, you’ll get a message saying “You are already playing a game” and you’ll be forced to leave.

I have no idea when this started happening. Ever since the beginning of Roblox? It does however happen 100% of the time as far as I’ve seen. To reproduce the bug, all you have to do is crash. Download the following rbxl file to try it out for yourself. Once you’re in the game, open the console and go to the server section. Wait a few seconds after you freeze, then close the application, and you should still hear the music playing and see Roblox in background processes of task manager.
crash.rbxl (13.2 KB)

Or if you'd rather not download the file, here's the script
function a()
    spawn(function()
        while true do
            wait()
            print("a")
        end
    end)
    spawn(function()
        while true do
            wait()
            print("a")
        end
    end)
    spawn(function()
        while true do
            wait()
            print("a")
        end
    end)
    spawn(function()
        while true do
            wait()
            print("a")
        end
    end)
    spawn(function()
        while true do
            wait()
            print("a")
        end
    end)
    spawn(function()
        while true do
            wait()
            print("a")
        end
    end)
    spawn(function()
        while true do
            wait()
            print("a")
        end
    end)
    spawn(function()
        while true do
            wait()
            print("a")
        end
    end)
    spawn(function()
        while true do
            wait()
            print("a")
        end
    end)
    spawn(function()
        while true do
            wait()
            print("a")
        end
    end)
    spawn(function()
        while true do
            wait()
            print("a")
        end
    end)
    spawn(function()
        while true do
            wait()
            print("a")
        end
    end)
    spawn(function()
        while true do
            wait()
            print("a")
        end
    end)
    spawn(function()
        while true do
            wait()
            print("a")
        end
    end)
    spawn(function()
        while true do
            wait()
            print("a")
        end
    end)
    spawn(function()
        while true do
            wait()
            print("a")
        end
    end)
    spawn(function()
        while true do
            wait()
            print("a")
        end
    end)
    spawn(function()
        while true do
            wait()
            print("a")
        end
    end)
    spawn(function()
        while true do
            wait()
            print("a")
        end
    end)
    spawn(function()
        while true do
            wait()
            print("a")
        end
    end)
    spawn(function()
        while true do
            wait()
            print("a")
        end
    end)
    spawn(function()
        while true do
            wait()
            print("a")
        end
    end)
end

while true do
    wait()
    a()
end

My device isn’t the most powerful, it’s just a £200 laptop, so it may take a bit more to crash you if you have a more powerful device.


closed #2

This topic was automatically closed after 1 minute. New replies are no longer allowed.


opened #3