Closed Bug 1169053 Opened 9 years ago Closed 5 years ago

unable to create GL context

Categories

(Core :: Graphics: CanvasWebGL, defect)

38 Branch
x86_64
macOS
defect
Not set
normal

Tracking

()

RESOLVED INACTIVE

People

(Reporter: nick, Unassigned)

Details

(Whiteboard: [gfx-noted])

Attachments

(2 files)

Attached file about support
Executing the following statement in the web console:

document.createElement('canvas').getContext('webgl')

there's a long pause, then null is returned.  FF 38.0.1 OSX 10.10.3.
After a reboot of the process, this is no longer the case.  Hopefully, the about:support log has something useful.
Comment on attachment 8611491 [details]
about support

Nothing too weird. Now that's it's working, try pulling the about:support again now that it works, and we'll check if the *-marked things below stop being empty. I think this is still just the symptom and doesn't help with the cause, though.

  "graphics": {
    "numTotalWindows": 2,
    "numAcceleratedWindows": 2,
    "windowLayerManagerType": "OpenGL",
    "windowLayerManagerRemote": true,
*    "adapterDescription": "",
    "adapterVendorID": "0x8086",
    "adapterDeviceID": "0x 166",
*    "adapterRAM": "",
*    "adapterDrivers": "",
*    "driverVersion": "",
*    "driverDate": "",
*    "webglRendererMessage": [
      ""
    ],
    "info": {
      "AzureCanvasBackend": "quartz",
      "AzureSkiaAccelerated": 0,
      "AzureFallbackCanvasBackend": "none",
      "AzureContentBackend": "quartz"
    }
  },
Indeed, there is a diff:

➜  tmp  diff about_support.text about_support2.text
9c9
<     "numTotalWindows": 2,
---
>     "numTotalWindows": 1,
109,110c109,110
<     "numTotalWindows": 2,
<     "numAcceleratedWindows": 2,
---
>     "numTotalWindows": 1,
>     "numAcceleratedWindows": 1,
120,122c120
<     "webglRendererMessage": [
<       ""
<     ],
---
>     "webglRenderer": "NVIDIA Corporation -- NVIDIA GeForce GT 650M OpenGL Engine",
Alright, yeah, nothing interesting there. It's succeeding at making contexts again, but that doesn't really help us with why. (Though it is weird that the VendorID is for Intel, whereas the WebGL renderer is NVidia. That's the ideal scenario, as long as we're doing it intentionally.
Whiteboard: [gfx-noted]
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: