New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 612138 link

Starred by 3 users
Status: WontFix
Owner: ----
Closed: Aug 2016
Cc:
█ h...@chromium.org
█ marc...@chromium.org
rohi...@chromium.org
songsuk@chromium.org
█ durga.behera@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Non-Regression: Weird behavior of marbles is seen in http://people.mozilla.org/~sicking/webgl/ray.html.

Project Member Reported by sc00335...@techmahindra.com, May 16 2016 
Version: 52.0.2734.0/8329.0.0 (Official Build) dev-channel veyron_jerry,peach-pit
OS: Chrome os

What steps will reproduce the problem?
(1) Go to http://people.mozilla.org/~sicking/webgl/raycolor.html and observe unwanted rastering of marbles

Expected: No unwanted rastering/flickering of marbles should be seen.
Actual: Instead unwanted rastering of marbles is seen.

NOTE:This is working fine in Quawks of same version[52.0.2734.0/8329.0.0]

This issue is seen from 47.0.2526.46/7520.33.0 beta channel daisy. Hence raising it as non-regression.

This is working fine in Linux and windows.
Actual_ray.html.png
138 KB View Download
In quawks.png
58.8 KB View Download

Comment 1 by durga.behera@chromium.org, May 16 2016

Cc: songsuk@chromium.org pucchakayala@chromium.org
Unable to reproduce the issue on Quawks using 52.0.2734.0/8329.0.0, will update once have the Peach-pit device(tomorrow).
cced MTV team to see if its reproducible on Jerry to confirm the same.

Comment 2 by songsuk@chromium.org, May 16 2016

Cc: rohi...@chromium.org
Reproduce the issue in 52.0.2734.0/8329.0.0 - Jerry, Pi

Not reproducible in Peppy, Cyan

Comment 3 by ajha@chromium.org, May 17 2016

Status: Untriaged (was: Unconfirmed)
Could reproduce this on the latest M-52(52.0.2734.0/8332.0.0) Dev-channel Pit as well.

Marking this Untriaged for further action.
Project Member

Comment 4 by sheriffbot@chromium.org, Jun 1 2016

Labels: -M-52 M-53 MovedFrom-52
Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 5 by sheriffbot@chromium.org, Jul 10 2016

Labels: -M-53 MovedFrom-53
This issue has been moved once and is lower than Pri-1. Removing the milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 6 by kbr@chromium.org, Aug 16 2016

Labels: -Pri-2 Pri-3
Status: Available (was: Untriaged)

Comment 7 by kbr@chromium.org, Aug 16 2016

Cc: -ajha@chromium.org -kavvaru@chromium.org marc...@chromium.org

Comment 8 by kbr@chromium.org, Aug 16 2016

Cc: -pucchakayala@chromium.org h...@chromium.org

Comment 9 by marc...@chromium.org, Aug 16 2016

Status: WontFix (was: Available)
Mali driver bug. I filed https://code.google.com/p/chrome-os-partner/issues/detail?id=56280 for it.

Comment 10 by djkurtz@chromium.org, Aug 16 2016 

Not necessarily a mali bug.  This could also be an issue with the demo itself.
These demos often have precision issues that are only exposed when using a GLES (ie non-Intel) driver.  Attached is the demo on elm, which uses Imagination graphics.
webgl_raytracer_elm.webm
918 KB View Download

Comment 11 by djkurtz@chromium.org, Aug 16 2016 

Note: Filed https://code.google.com/p/chrome-os-partner/issues/detail?id=56282 for possible Imagination specific issue in #10.

Comment 12 by marc...@chromium.org, Aug 16 2016 

yeah it could be a precision issue (I know this demo had precision issues in the past). Let's track them as separate bugs for now..
►

Sign in to add a comment