Search Issue Tracker

Fixed in 4.5.X



Found in


Issue ID




Serialization error thrown after changing Asset Serialization mode to Force Text

Deployment Management


To reproduce:
1. Open the attached project (
2. Notice serialization error in the console
3. Clear this error
4. Select Assets - > Reimport All
5. Error pops-up again
6. Go to Edit->Project Settings->Editor
7. Change Asset Serialization Mode from Force Text to Mixed
8. Reimport again. No error this time
9. Change Asset Serialization Mode to Force Text. Error is thrown again

Could not serialize text file projectsettings/projectsettings.asset because an error occured - we probably ran out of memory.

Comments (14)

  1. virtualbob

    Jun 09, 2019 07:06

    I'm using 2017-2018-2019. Still getting these errors....

    Starting to think maybe wasting my money on Unity assets I get burned for and become unsupported (Pretty much right after I buy them and start using them), and my time on Unity itself is a bad idea. All I see is a software riddled by stupid issues, new versions of stead of just addressing the issues... then the new versions having the same issues and new ones... and utter-lack of backwards compatibility should almost be an embarrassment for Unity.... but still seem proud.

    Thinking it's time to look for an Alternative, or just buy a real engine. In the end time and money would have been less.

    And trying to use unity for anything bigger then mobile games is a fail, unless you want to spend 70% of your time looking at Unity in a "Not responding" state...

  2. Sam Bauwens

    May 29, 2014 12:08

    I'm still having the issue after upgrading to unity 4.5

  3. benbritten

    Mar 07, 2014 02:14

    This is happening still in 4.3.4f1

  4. jerome-lacoste

    Mar 06, 2014 19:51

    I am hitting the following issue on 4.3.3f1:
    * Editor settings are set to ForceText
    * ProjectSettings.asset has now been converted to binary

    This is really annoying and prevents merging branches properly.

    My workaround is to do as in:

    1. add this function to one of your Editor class

    [MenuItem("Tools/PlayerSettingsPresets/ProjectSettings serialize Repair")]
    public static void PlayerSettingsPresets_ProjectSettings()
    PlayerSettings.SetScriptingDefineSymbolsForGroup(BuildTargetGroup.Unknown, "");
    AssetDatabase.Refresh(ImportAssetOptions.ForceUpda te);

    2. run it

    3. force a save of the ProjectSettings. I usually do this by: open the BuildSettings, toggle off/on one of the scene in the list of scenes, and force a save by doing CTRL-S

  5. iaanus

    Mar 06, 2014 09:34

    Fact is that bagelbaker's workaround doesn't work on my setup. It does appear to fix to the problem, but the fix is only temporary: as soon as you change something (beats me if I know what "something" triggers the bug) the projectsettings file becomes binary again.

  6. privman

    Mar 04, 2014 17:45

  7. iaanus

    Feb 25, 2014 08:54

    It says "fixed", but in which version? The bug is still present in 4.3.3f1 and it's not listed as fixed in the release notes of 4.3.4. I'm not going to upgrade to 4.3.4 just to check that, because upgrading Unity (even minor upgrades!) is not always hassle-free (this bug is an example).

  8. MrCranky

    Feb 20, 2014 14:00

    Worth noting that when I check back in the version control history, this file was changed from a text to a binary version during the 4.2 -> 4.3 upgrade, even though the project is and always has been set to use text serialisation for assets.

  9. technicat

    Feb 10, 2014 10:29

    The bug description says it's not a regression, but I'm pretty sure it is, which should argue for a higher priority.

  10. MrCranky

    Jan 23, 2014 13:02

    I can confirm this here: large project, Forced Text used for serialisation, and when other people make changes to the file that I pick up through source control, it throws this error and my local file is saved. The file is definitely binary. It does however seem to keep those external changes though, so it's loading the changed settings just fine, then decided they need re-saved, and writing something subtly different out after putting this error out to the console.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.