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

Issue 706648 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

pp::Graphics3D is null when setting PP_GRAPHICS3DATTRIB_SAMPLES

Reported by dmur...@aconex.com, Mar 30 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.110 Safari/537.36

Steps to reproduce the problem:
In our overridden pp::Instance function we do the following:

    ...
    const int32_t attrib_list[] = {
            PP_GRAPHICS3DATTRIB_ALPHA_SIZE, 0,
            PP_GRAPHICS3DATTRIB_DEPTH_SIZE, 24,
            PP_GRAPHICS3DATTRIB_SAMPLES, 2,
            PP_GRAPHICS3DATTRIB_SAMPLE_BUFFERS, 1,
            PP_GRAPHICS3DATTRIB_NONE
    };

    context = pp::Graphics3D(this, attrib_list);
    ...

This has been creating a non null context since development began for us 18 months ago.
Since Version 58.0.3029.33 beta (64-bit) on Windows we have been getting a null context.

By reducing the attribute list to:

    ...
    const int32_t attrib_list[] = {
            PP_GRAPHICS3DATTRIB_ALPHA_SIZE, 0,
            PP_GRAPHICS3DATTRIB_DEPTH_SIZE, 24,
            PP_GRAPHICS3DATTRIB_NONE
    };

    context = pp::Graphics3D(this, attrib_list);
    ...

We are able to get a non null context but with reduced image quality.

What is the expected behavior?
We would like to be able to use multi sampling on browsers that were previously able to use multi sampling.
We would like to know if this is a new bug in the Beta release or a change in behaviour that will be in newer chrome releases.

What went wrong?
We are no longer able to use multi sampling on browsers that previously supported it

Did this work before? Yes Version 57.0.2987.133 (64-bit)

Does this work in other browsers? Yes

Chrome version: 58.0.3029.33  Channel: beta
OS Version: 10
Flash Version:
 
Components: Internals>Plugins>Pepper>SDK

Comment 2 by kbr@chromium.org, Mar 30 2017

Cc: kbr@chromium.org piman@chromium.org geoffl...@chromium.org jmad...@chromium.org
Components: -Blink>WebGL Internals>GPU>Internals
Do you have a Pepper plugin that you could provide as a test case?

I doubt we've changed the Pepper implementation recently, but have changed the underlying graphics system significantly. This is probably an accidental regression.

Labels: Needs-Feedback Needs-Triage-M58

Comment 4 by dmur...@aconex.com, Mar 30 2017

This seems to be fixed in Version 58.0.3029.41 beta (64-bit)
Project Member

Comment 5 by sheriffbot@chromium.org, Mar 30 2017

Cc: durga.behera@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "durga.behera@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Comment 6 by piman@chromium.org, Mar 30 2017

Status: WontFix (was: Unconfirmed)
Closing per #4

Sign in to add a comment