I was playing in the editor and I hit play (maybe pause too?) to stop the game and the editor after an alert box with the error “too many roots” is now frozen
happened a couple of times…
never had this error before (same game) on unity v <= 3.1
still having this…
Could your project me corrupted from an earlier crash? Make a new project and import small groups of files over at a time, checking for errors as you go, see if that helps?
I get this error when the editor is very close to being out of memory.
I never had this same error in 3.1 but did have out of memory errors.
Check if unity is using over 1.6gb of RAM when it crashes… if it does there are 2 ways I found for liberating up some memory for Unity while keeping your scene the same :
- Minimize / Restore the unity editor window. The GC kicks in and cleans off everything. Works way better than run-time GC that accumulates everything (no leak… but once it’s there… it stays there).
- Change your quality settings for the editor mode to something that uses 1/2, 1/4 or 1/8 of the texture size (Simple or Poor… ect)
it’s not something that I can reproduce, I’ve had it 2/3 times only since my upgrade to 3.2 so I can’t use an approach like that.
will check the memory next time it’ll happen
Well you could still create a new project and import things over, at the very least you’ll be able to start fresh and with new clean project files that sit outside the project assets themselves, (all that library stuff we don’t mess with) and if there is something broken, it could well be in there.
A bug report was filed for this about a week ago (case 391832) but it is still under investigation.
ok thank you, can you please tell me how can i follow it? edit: thanks I’ve seen your answer in the other thread
if it can be useful it happened again and the memory used was only around 800MB and I had a lot of memory still free (8GB)
Is there a known solution to this problem? I keep getting this error every hour or so… it is becoming most annoying.
Unfortunately, the bug report was not followed up with an example that reproduces the bug so the QA team didn’t have much to go on. It would be great if you could file a new report, ideally with a project that shows the problem and any extra detail that might be relevant.
I just can’t reproduce it.
It seems to happen with any project. It seems to always occur when I go back to the Unity Editor when switching from Visual Studio.
Not sure if it matters, but I am running windows 7 64 bit.
Some information that might help. This message is an internal mono message got it while using mono (without unity) on windows several times. For unity it seems to happen for me if I attach the debugger and stay in a breakpoint too long.