Studio Breaking Bug: "Serializer::load can't read header" Happens to EVERY autosave, Studio Crash when Pressing Stop the 2nd time you use Play

[TEMPORARY FIX}
Open current Save, Go to Roblox, revert current place version to an older one, Open now reverted Save, Erase Everything from Reverted, Paste everything from Current, Publish.
This has shown no evidence of still being broken, and it points towards that save being permanently ~infected~ by the bug, but older saves are safe, also, it doesnt seem to be related to content present in save, or size of it, just a general bug that after it happens once, will happen forever in that save, publishing a new version of current wont help, only ways to fix seem to be: Reverting and Pasting new changes, or, Creating a new place and pasting your content over there.

Hey, so i’ve encountered a rare bug, only other post i’ve found about it is 3 years old and has no answers at all.

This bug is literally making it impossible for me to Continue the Development without having to Publish and Reopen DevStudio after EVERY time i use the [Play] function, because if i use it again, it’ll 100% Crash after Pressing [Stop] if i use Play again, and the Autosave will be Corrupted.

Error Message Is:

[Sorry, this place could not be loaded. Details: "Serializer::load can’t read header"

If you continue to encounter this error, please report it on the Developer Forum.

Incident ID: 5217901447363945461]

Only changes i made since this started happening were REALLY nothing different, just normal dialogue, variables and UI, and this bug just made my game crash and lose 2 hours of progress, because Autosaves are now corrupted.

Don’t know if it helps, but my current Backup Savefile Weights 3,94mb, so its really not that much, even compared to other places of mine that are fairly empty.

I’m lost in how to deal with this, since this seems to be a thing for a long time, and found no real information about it other than “it happens sometimes”, no idea if it stops by itself, no idea if i can revert and it’ll go away, i’m really lost, so i hope someone can help me with this.

Can’t report this as a bug either, since Memberships are still not being upgraded.

edit: Tried reverting to an older save and just pasting everything new there, seems to be working for now, if it’s a fix i’ll create a post about it, so other people can potentially not be as frustrated as i was when i saw nothing about this bug.

3 Likes

I have the exact same issue.
I bought a new laptop and the bug started to happen.

1 Like

it only does that if the file size is 0kb

i also think its from roblox being down and being unable to create an autosave

someone else was having this problem not long ago actually… odd to say the least

potential studio bug

try making a local save on your computer
open that local save from your files
click publish to roblox
overwrite the existing copy of the game

see if that works perhaps

file size was normal when i checked, but other people seem to be having the 0kb bug, so i will assume i am remembering it wrong.

Nothing related to uptime, as Roblox was working and this bug was replicable, always crashing when Using STOP when using Play for the 2nd time in a session.

Publish was working, Load was working, everything normal.

also, Autosave are not dependent on the internet, it saves to your computer.

Publishing still works, what was happening was: Autosave being Corrupted and Studio Crashing when using Stop during the 2nd Time you use Play in the same session.

found a temporary fix, but can’t be sure it it’ll work for a long time, it’s listed as first thing in the post (edited)

[TEMPORARY FIX}
Open current Save, Go to Roblox, revert current place version to an older one, Open now reverted Save, Erase Everything from Reverted, Paste everything from Current, Publish.