Chrome 30 crashes during texture rendering about jsc3d

[GoogleCodeExporter]

That's too bad. 

It looks very similar to a known issue 
http://code.google.com/p/chromium/issues/detail?id=277297. It is tested to be 
relevant to some incorrect optimization for nested loops in V8 javascript 
engine for Chrome 29 and above, which internally results in an 
EXC_BAD_ACCESS/KERN_PROTECTION_FAILURE error and makes the browser crash down.

A guy from the Chromium team told me that the problem does not recur on early 
built of Chrome 32. They are working on to fix this bug in future release.

For now, you could try jsc3d's (experimental) webgl rendering backend to avoid 
this problem. 

To achieve this, first download the latest jsc3d.js 
http://jsc3d.googlecode.com/svn/trunk/jsc3d/jsc3d.js and jsc3d.webgl.js 
http://jsc3d.googlecode.com/svn/trunk/jsc3d/jsc3d.webgl.js from the repository 
and include them in your application page.

Then, enable webgl rendering using an currently undocumented startup parameter 
'Renderer' before initialization of the viewer instance:

  ...
  viewer3d.setParameter('Renderer', 'webgl');
  ...

By setting this, jsc3d will try to launch its webgl accelerated rendering 
backend to replace the traditional software rendering routine where webgl is 
available. It's harmless for browsers which do not support webgl.

I modified your demo using the method mentioned above and it seems to work fine 
in my own test. You can get it in the attacment.

Jsc3d's webgl support is still very experimental at this moment. You are 
welcome to submit issues if you have problem using it.

Original comment by [email protected] on 12 Nov 2013 at 4:44

Attachments:

• bug_demo_2.zip

[GoogleCodeExporter]

Thanks a lot for your support.
I will make many tests and so I will report you if I have any problem with 
webgl.
Great library by the way.

Original comment by [email protected] on 12 Nov 2013 at 5:52