High CoreScriptMemory usage

I’ve been reaching 300 MB CoreScriptMemory usage lately, making my game lag on the client side, without mentioning reaching 2500 MB server memory, 1250 MB being untracked.

Is CoreScriptMemory an issue that I made with my scripts or is it by roblox? I’ve checked my scripts and they only use 3 MB.

I tried looking into my scripts one byone and and disabling everything, but the CoreScriptMemory is still going up insanely.

And this is what I use

Are you testing in Roblox studio or the Roblox client?

Roblox studio uses alot of memory itself, try testing this in your game on the Roblox client.

I’m testing on the Roblox Client and the values just get higher and higher without any scripts running

Perhaps you have a memory leak in one of your scripts?

And this only happens in your game? or other games too?

I have no scripts running right now and the corescriptmemory is at 120 MB after a few minutes

I’m reaching 100 MB lua heap in a baseplate with no scripts and corescriptmemory is at 80 MB with NOTHING, just a pure baseplate

And just keeps going up

Try reinstalling the Roblox client.

That happend to me too, it stopped next day, I still can’t know what made that

It’s not that, other players lag on my games too, its not only me

I see… Let’s hope it stops soon tho

All your games? maybe try reinstalling Roblox studio.

It may be a plugin from studio that placed something random like this in your game.

Hey there,

CoreScriptMemory is something you should ultimately not be worrying about, as that is not something you can tangibly update or read. CoreScriptMemory (or I’d assume at least), is a tracker for CoreScripts themselves. Safe to say that this is most likely a ROBLOX issue, and that you shouldn’t worry! (at least I believe.)

ROBLOX is known to have memory leaks on their side and it’s ultimately something we’re just going to have to wait for them to fix. (It’s not like they’re perfect! :tongue:) Just a couple days ago someone discovered that just resetting causes memory leakage, and it consistently builds up client memory!

Also, another thing that might help is that if you’re running this in ROBLOX Studio that it accounts for the entire program, and not just the client, so there might be underlying issues there as well(?)

1 Like