4 ms·

Chrome V38.0.2125.104 on 64-bit Ubuntu 14.04

by KhalilK 12y ago

laurencei 12y ago
I'm on the exact same Chrome version, but on Windows 7 - no issues here.
- exDM69 12y ago
  The difference is the OpenGL implementation. On Windows, Chrome uses the ANGLE middleware to implement WebGL. It's a layer that implements the OpenGL ES 2 API on top of Direct3D 9. That solves quite a lot of driver quality issues (at the cost of some overhead). So the question is, which GPU/driver was being used on Linux.
exDM69 12y ago
What GPU/driver are you using? This looks like either a driver bug or some unsupported combination of pixel formats. Unfortunately, WebGL doesn't solve these compatibility issues that are inherent to OpenGL and running on a wide variety of hardware and drivers.
- KhalilK 12y ago
  I see. product: 2nd Generation Core Processor Family Integrated Graphics Controller vendor: Intel Corporation driver=i915
  - exDM69 12y ago
    Unfortunately, that generation of Intel GPUs is known to be quite bad in performance and having very buggy OpenGL drivers. I don't know if that's the cause of the issue you're seeing but don't expect to run any fancy 3D on Linux with that GPU.
    - zurn 12y ago
      It is the same driver as the later Intel models. It is one of the very few drivers that are not blacklisted by Chrome on Linux, owing to its unbugginess.
      - exDM69 12y ago
        I know, but that doesn't mean that there aren't bugs or missing features specific to that GPU model (hardware or software). But I can't be sure whether this particular issue is a driver bug or just an unsupported combination of pixel formats (FRAMEBUFFER_INCOMPLETE hints at that). WebGL spec requires certain of pixel formats to be supported but either the test case is using some combination that isn't guaranteed to be supported or the driver+hw combination doesn't actually support everything required by the spec. Intel has made huge improvements since the days of the i9xx series of GPUs. They were miserably bad from a programmer's standpoint.

Chrome V38.0.2125.104 on 64-bit Ubuntu 14.04

by KhalilK 12y ago

Chrome V38.0.2125.104 on 64-bit Ubuntu 14.04

laurencei 12y ago

I'm on the exact same Chrome version, but on Windows 7 - no issues here.

exDM69 12y ago
The difference is the OpenGL implementation. On Windows, Chrome uses the ANGLE middleware to implement WebGL. It's a layer that implements the OpenGL ES 2 API on top of Direct3D 9. That solves quite a lot of driver quality issues (at the cost of some overhead). So the question is, which GPU/driver was being used on Linux.

exDM69 12y ago

What GPU/driver are you using? This looks like either a driver bug or some unsupported combination of pixel formats. Unfortunately, WebGL doesn't solve these compatibility issues that are inherent to OpenGL and running on a wide variety of hardware and drivers.

KhalilK 12y ago
I see. product: 2nd Generation Core Processor Family Integrated Graphics Controller vendor: Intel Corporation driver=i915
- exDM69 12y ago
  Unfortunately, that generation of Intel GPUs is known to be quite bad in performance and having very buggy OpenGL drivers. I don't know if that's the cause of the issue you're seeing but don't expect to run any fancy 3D on Linux with that GPU.
  - zurn 12y ago
    It is the same driver as the later Intel models. It is one of the very few drivers that are not blacklisted by Chrome on Linux, owing to its unbugginess.
    - exDM69 12y ago
      I know, but that doesn't mean that there aren't bugs or missing features specific to that GPU model (hardware or software). But I can't be sure whether this particular issue is a driver bug or just an unsupported combination of pixel formats (FRAMEBUFFER_INCOMPLETE hints at that). WebGL spec requires certain of pixel formats to be supported but either the test case is using some combination that isn't guaranteed to be supported or the driver+hw combination doesn't actually support everything required by the spec. Intel has made huge improvements since the days of the i9xx series of GPUs. They were miserably bad from a programmer's standpoint.