Avoid UnitySetInput(bool enable) in 4.2.1f4, causes lockups?

is anyone else experiencing this with latest update 4.2.1f4 or just me… when executing method UnitySetInput(); the Windows App locks up?

I’ve found that UnitySetInput throws an access violation if called from the app thread (from within InvokeOnAppThread). It seems to work if called from the UI thread.

in my case it was within the InvokeOnUIThread and throws the access violation… they’re not able to replicate the issue, so I’m at a bit of a loss on this one.

for now, i’m chalking it up to something stupid I’ve done or something odd after upgrading… I don’t have time to test a cleaned up or fresh sample build yet.