Chrome Native Client Issue - NativeClient: NaCl module crashed

I am getting

Refused to execute inline event handler because it violates the following Content Security Policy directive: "script-src 'self' chrome-extension-resource:".
NativeClient: NaCl module crashed

With the most basic of tests.

Any help?

 

Appears to be the onload attribute in the embed tag is not allowed any more in Chrome. Removing that gets rid of the error. However the nacl is still crashing...

 

Thanks! Great timing on my testing then! Brilliant!

 

I'm using Unity 4.3.1 and having the same issue here. Is this planned to be fixed in the next release, having to maintain multiple machines with Unity Pro just to do NaCL builds isn't ideal.

 

That is good to hear, but are there any plans to fix this regression? Thanks!

 

Have you tried running Unity 4.2 and Unity 4.3 on the same machine? I've been trying to make it work today and it's a disaster. The installer doesn't create separate icons for the versions, and the project files are completely incompatible with each other. When I open my Unity 4.3 project with 4.2 it gives a warning about data loss and encourages me to exit. Should I just ignore this warning, or is it there for a reason? Clicking continue forces a reimport on the project, making it incompatible with 4.3.

Is there an ETA for the NaCL regression to be fixed? Do regressions get a higher priority than other issues, seeing as some people are now dependent on features that used work?