Memory leak with sounds

Bug Reports Engine Bugs
#1

don’t run this script on yourself unless if you acknowledge that this code is a memory leak and WILL make your computer act funny until you restart it.

local player = game.Players.LocalPlayer
for i = 1, math.huge do
	local sound = Instance.new("Sound", player.PlayerGui)
	sound.SoundId = "http://www.roblox.com/asset/?id=130797915&ver=" .. i
	sound.Volume = 0
	sound:Play()
	wait()
end

Put that in a LocalScript and whoever the LocalScript runs on will end up memory leaking it.

Sound instances that use the same large sounds leak Streaming Sounds memory on the server
#2

What sort of funny behaviour are we talking about?

#3

Basically, it’s a memory leak. Even though you end up exiting the game, everything’s still in the RAM and your computer acts funny until you restart it

#4

Basically, it’s a memory leak. Even though you end up exiting the game, everything’s still in the RAM and your computer acts funny until you restart it[/quote]

That was my really, really poor attempt at humour, going to be honest. Cool though.

#5

Just thought it should be known that xSIXx is the original finder of this issue, and was planning on reporting it.
Anyways, to fix this issue, just don’t allow redundant assets to be Preload()ed.

PS: this isn’t nearly as bad as the delay() leak.

#6

Basically, it’s a memory leak. Even though you end up exiting the game, everything’s still in the RAM and your computer acts funny until you restart it[/quote]
Also, this is not true. When the ROBLOX process eats up a lot of RAM, Windows tries to compensate by pushing other processes and services to the background to conserve memory. A reboot makes the “recovery” process quicker, but as long as you’re patient (and the ROBLOX process is indeed not running), then the processes and services will restore back to their normal state.

#7

I think this is more of “I tried to download several terabytes of data and it ate my ram”

#8

Basically, it’s a memory leak. Even though you end up exiting the game, everything’s still in the RAM and your computer acts funny until you restart it[/quote]
Also, this is not true. When the ROBLOX process eats up a lot of RAM, Windows tries to compensate by pushing other processes and services to the background to conserve memory. A reboot makes the “recovery” process quicker, but as long as you’re patient (and the ROBLOX process is indeed not running), then the processes and services will restore back to their normal state.[/quote]
Yeah, well said. And yes, xSIXx does deserve credit as the one who showed me the issue.

#9

Sometimes the sound of a game never stops, even if you exit the client in game, you have to promp the task manager and exit roblox player from there, but not sure if this is some sort of the same?

#10

Basically, it’s a memory leak. Even though you end up exiting the game, everything’s still in the RAM and your computer acts funny until you restart it[/quote]

My computer does that whenever I play anything.
[size=2]Accidentally clicked the thank you button.[/size]

#11

Have you tried this with decals?

#12

I ran it, and it didn’t seem to do anything. It hit the x32 memory limit then crashed before anything.
Try it with the decal which anaminus uploaded… hehe.