Just updated to 8.0.1489 (possibly from 8.0.1483 or earlier).
Now at random times I will get an error inside the Unity 3D game engine editor.
It’s being overly touchy about what Unity does, particularly involving threads. What change did you make that would do this? You need to revert it ASAP.
Avast is also causing a break in compiled programs.
Have you tried adding it to gloabal exclusions and adding to the behavior shield exclusions? If it has something to do with Avast then it would be in the Avast logs.
just curious, what happens if you setup sandbox to ask ?
Just wanted to chime in with this, It seems there is a bug currently with the Unity Engine causing some players (running avast) to find there games abruptly ending. (being affected by this.) The Unity team has made a new mono.dll which should work with the game to fix/make the engine stable with Avast. http://forum.unity3d.com/threads/172759-Unity-4-0-1f2-and-avast-8-0-1482-quot-getThreadContextfailed-quot-error/page3 I think it’s worth mentioning to the developers so they can compile there games with this bug fix.
Many have done this in the Unity Forums but are still having issues with this error message. Unity is currently pointing the blame at Avast so its just waiting for someone to figure out who’s side the problem is.
It seems Unity may have found a fix for this the main problem is that the next fix push for it will be in the next Unity engine version (v4.2)
Just wanted to let you know as this will need to be rolled out by the publishers if the Unity Engine was installed using an embedded version.
Should mention the rise in reports that http://forum.unity3d.com/threads/172759-Unity-4-0-1f2-and-avast-8-0-1482-quot-getThreadContextfailed-quot-error/page5 A/V version 1489 is causing users to get this error. (could it be related to a policy change?) Just wanted to provide more info. Not sure if it helps but its worth informing you guys about it.
See if that helps…
Uncheck: Settings → Toubleshooting → Enable hardware-assisted virtualization
Have done that however we are still getting the error showing up. Will continue to troubleshoot.
Did you reboot after the change…??
Yes we did reboot but it’s still showing the error during gameplay across multiple Unity Engines.
Have spoken to Unity and they have said they are working on an update to the engine which will prevent this issue from happening again with Avast. Its worth mentioning that the gaming publisher will need to upgrade there engine to the latest version in-order to fix this issue with Avast.