encima / encima/jsc3d

Chrome 30 crashes during texture rendering

Open
#47 0 comments 0 reactions 0 assignees View on GitHub
auto-migrated Priority-Medium Type-Defect
Dominant language
HTML
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

```
= What steps will reproduce the problem?
1. Open Chrome 30.0.1599.101 (Windows or Mac)
2. Go to this URL : http://www.fabzat.com/tmp/bug_demo/
3. The browser often (or sometimes ?) crash after loading textures

= What is the expected output? What do you see instead?
Expected : 3D model is loaded normally
Reality : Chrome crashes with the "aw snap" message
http://fabzat.com/tmp/bug_demo/aw-snap.png

= What version of the product are you using? On what operating system?
I can reproduce the problem on WIndows & Mac with Chrome version 30.0.1599.101
(tested on 5 differents computers)
The version of the lib used is "JSC3D 1.4.2 full release"

= Please provide any additional information below.
The problem occurs in texture smooth rendering when calling method
"transformVectorZs" (the first of two).
I tried to replace my textures with textures from one of the demos provided
(bank), result is the same.
The problem does not occur if I remove texture files from server (aka 404
errors on image files).
Problem occurs more often if webpage if on a remote server and not in a local
network.
Problem occurs on the first load only. When files are in the browser cache, the
problem dos not occur anymore.
Files to reproduce can be found here :
http://fabzat.com/tmp/bug_demo/bug_demo.zip

I understand that this is a browser bug and not a jsc3d bug. But I need to find
a workarournd for my production use.

Thanks for your help
```

Original issue reported on code.google.com by `laurent....@fabzat.com` on 12 Nov 2013 at 12:13

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the linked bug_demo URL and the JSC3D 1.4.2 texture smooth-rendering path, especially the first call to transformVectorZs. Compare loading with textures available versus 404 responses and cached assets; done means identifying a reproducible workaround that prevents the Chrome crash while the 3D model loads.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.