WebGL Three.js examples crashes

[GoogleCodeExporter]

What steps will reproduce the problem?
- Open the WebGL examples at http://mrdoob.github.com/three.js/ (for example: 
http://mrdoob.github.com/three.js/examples/webgl_shading_physical.html). Most 
of them will crash the CEF Client.

What is the expected output? What do you see instead?
Chrome for Windows works well on those Three.js examples.

What version of the product are you using? On what operating system?
v. 1.1180.832 on a Windows 7 on a HP EliteBook 8440p with Nvidia NVS 3100M

Please provide any additional information below.
I ran the CEF client even in Debug mode and got messages of failed assertion: 
File libGLESv2\Texture.cpp, expression: "mD3DFormat != D3DFMT_UNKNOWN"

Original issue reported on code.google.com by smnle...@gmail.com on 20 Nov 2012 at 4:08

[GoogleCodeExporter]

I believe that assertion was fixed recently. And it was also benign (wouldn't 
cause a crash).

That WebGL sample doesn't crash on my system (within Chrome 23.0.1271.64 m, 
which uses ANGLE r1275). What version of ANGLE does the CEF Client use? What 
module does the crash occur in?

Original comment by nicolas....@gmail.com on 20 Nov 2012 at 4:43

[GoogleCodeExporter]

ANGLE was the one distributed with Chromium Embedded v. 1.1180.832.
In Chromium Embedded\cef_binary_1.1180.832_windows\Release I
have*libGLESv2.dll that is v1.0.0.1046
*, so I think ANGLE its a bit older than the one used by Chrome 23 (that is
the version I use, too).
*> What module does the crash occur in?*
Even within Debug in Visual Studio 2010, it is difficult to say... It ends
in oneexit.c. from libCEF. I have the binary version of libCEF.
To be more precise I should rebuild the libCEF, but sorry I have no time to
do that...

Do you think I can simply replace libGLESv2.dll with a more recent build?

Original comment by smnle...@gmail.com on 20 Nov 2012 at 5:24

[GoogleCodeExporter]

I tried to use the Chrome libGLES dll, and the CEF client crashes (I must
say that I do not have libEGL aligned to the libGLES version, as libEGL
seems not used by Chrome).
So I think the problem is in the CEF library...

2012/11/20 Simone Lelli <smnlelli@gmail.com>

Original comment by smnle...@gmail.com on 20 Nov 2012 at 5:39

[GoogleCodeExporter]

Chrome definitely uses libEGL.dll as that is the only way to load ANGLE.  
You'll want to make sure you have matched libGLES and libEGL libraries, but 
other than that I don't see why you wouldn't be able to drop new ANGLE 
libraries into CEF.  That said, sometimes there are changes in ANGLE+Chrome 
that are interrelated and need to be kept together (for example moving between 
Chrome 21 and 22). I don't know much about Chromium Embedded, nor do I know 
what version of Chrome that version you have is based off of. 

Original comment by dan...@transgaming.com on 28 Nov 2012 at 6:42

[GoogleCodeExporter]

I was using Chromium Embedded Framework 1. This is a single-process version
of CEF, and this has the problems with three.js site examples. Then I
downloaded and tried the *Chromium Embedded Framework 3*, that as the same
multi-process architecture of Chrome Browser, and *this works well on
thee.js examples*!!

So it is a problem in CEF1... and not specific of ANGLE... (used by CEF 1
and 3).
Maybe a problem with resource loading (e.g shaders?) in CEF 1...

Thank you for your support
S. Lelli

Original comment by smnle...@gmail.com on 29 Nov 2012 at 3:46

[GoogleCodeExporter]

Thanks for looking into it. Closing as invalid.

Original comment by nicolas....@gmail.com on 29 Nov 2012 at 3:55

• Changed state: Invalid