gc: too many threads, crash using Unity 4.2

To be honest i've worked with a lot of different Unity versions (started with 2.6 i guess) and even on different hardware and OS and i never had an "unexpected" crash. Here at home i still have a quite old WinXP 32Bit dual core with 3GB memory and i've run all Unity versions (even at the same time) without any problems. At work i have a Win7 machine and never had a crash.

Too many threads sounds suspicious. Do you use any kind of threads in your game (explicit or implicit!)? A lot people are not aware of the fact that almost all "async" callbacks in .NET are implemented via a seperate thread.

You gave not much information about your project / system / ...

Does this also happen when you work in an "empty" project? Empty means really empty. No frameworks like NGUI, .... since they implement a lot editor features. It's difficult to track down such problems especially when you can't nail it down to a certain action / script / asset / component.

ps. I never experianced a crash due to a memory leak in Unity. Are you sure that it's not you that causes the memory leak due to misusing the API like duplicating materials meshes at edit mode, ....?

Yes, I can confirm that it happens in an empty project. I created a new project, added only a cube GameObject, moved the x-position slider back and forth a few times, and then I got the error and Unity shutdown. The editor was still in scene view, I did not press Play or anything, so I am pretty sure it does not have anything to with my own code/projects. This of course, leaves me clueless, since I did not find a solution yet. I will update my graphics card drivers now, because you never know. (Edit: That didn't help) Thanks for your comment.

I am facing the same scenario, except Win8 x64. It's a development machine so RA$$anonymous$$/CPU/GPU are all very up to date and I've never experienced this issue on a build before 4.2. Right now 4.2 is unusable on my system because it'll crash within two $$anonymous$$utes of being launched. Any info would help greatly if someone figures this out.

Report it as a bug

It seems very much like the problem exists only with a second monitor attached.

@pprnts I don't think that's the issue. I have a dual screen setup, too, and I've never heard of this occurring. I doubt dual screens would be causing a 'too many threads' error, either.

I had this on a dodgy netbook with integrated graphics (Intel ofc...only the best).

I read somewhere that Unity 4.2 threw some kind of error when trying to render a material-less object or materials with NoName, or something random like that. Try sticking a texture on your cube in the empty project and see what happens then.

Also, check the crash logs to see exactly what was going on before the CRASH! entry

It only shows up with a second monitor. I can run dual monitors fine with any other programs (including $$anonymous$$aya), but if I try a second screen with U3D 4.2 it crashes every time, guaranteed, always with the graphics card thread issue.

Are you running Unity on the second monitor, or the first? Also what graphics card are you using?

Laptop is development machine that has been used for Unity in the past, graphics are unfortunately Intel(R) HD Graphics 3000 integrated. :/ This happens with Unity on either screen, have tried from a cold reboot too, but no matter what with two monitors I can't make it more than three $$anonymous$$utes without the crash. The only thing you notice in Unity beforehand is everything starts to slow down (like resizing a property window, actual window is ghosting behind your movement a bit) and then boom. Does not occur on desktop machine with A$$anonymous$$D 7970 as main graphics card, but this has been the machine I've used since Unity 3.x and this is the first time I've seen this problem (4.2).

Ah. I've had issues with Intel(R) HD 4000 with Unity (I actually managed to melt one with it), though not quite as you're describing. I'm really not sure what the problem would be here, it does sound like it's an issue with some of Unity 4's compatibility with the graphics card.

I now have the same problem. Dell XPS 15 with Intel HD3000 and Geforce with Optimus. Laptop and Second $$anonymous$$onitor on Displayport, which is connected to the Intel Graphics Card functions well BUT when I'm connecting my Oculus Rift with HD$$anonymous$$I (connectet to Nvidia Card) as third monitor Unity crashes 5 seconds after start with "too many threats". Seems to have something to do with Nvidia Optimus, when I'm connecting Oculus to Displayport without anything on HD$$anonymous$$I everything is okay again.