Closed Bug 1640428 Opened 4 years ago Closed 2 years ago

Crash in [@ glgConvertTo_32<T>]

Categories

(Core :: Graphics: CanvasWebGL, defect, P3)

Unspecified
macOS
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox-esr68 --- wontfix
firefox76 --- wontfix
firefox77 - wontfix
firefox78 --- wontfix

People

(Reporter: Sylvestre, Assigned: jgilbert)

Details

(Keywords: crash)

Crash Data

This bug is for crash report bp-e5f02a06-b509-4394-ac9f-c53150200523.

Top 10 frames of crashing thread:

0 libGLImage.dylib void glgConvertTo_32<GLGConverter_BGR8_ARGB8,  
1 libGLImage.dylib glgProcessPixelsWithProcessor 
2 AppleIntelHD5000GraphicsGLDriver AppleIntelHD5000GraphicsGLDriver@0x4edf67 
3 GLEngine GLEngine@0x1a3ba 
4 libGL.dylib glTexImage2D 
5 XUL mozilla::gl::GLContext::raw_fTexImage2D gfx/gl/GLContext.h:1648
6 XUL mozilla::gl::GLContext::fTexImage2D gfx/gl/GLContext.cpp:2550
7 XUL mozilla::DoTexImage dom/canvas/WebGLTextureUpload.cpp:642
8 XUL mozilla::webgl::DoTexOrSubImage dom/canvas/TexUnpackBlob.cpp:395
9 XUL mozilla::webgl::TexUnpackSurface::TexOrSubImage const dom/canvas/TexUnpackBlob.cpp:885

My partner is experiencing this on Facebook, fails every time.

She crashes with 76 and 76.0.1.. On a OS X 10.11. I guess it is a driver issue.

I have easy access to the laptop

I think it was crashing on a 360 photo which seems to use WebGL

[Tracking Requested - why for this release]:
With 5630 crashes on release, I don't think it deserves a dot release but a release manager should track this (and the volume of crashes have been increasing).
It causes Facebook to be unusable on some kind of Mac...

I don't think it is a regression in Firefox but a change in usage of WebGL downstream

Component: Canvas: 2D → Canvas: WebGL
Flags: needinfo?(jgilbert)
Flags: needinfo?(jbonisteel)

I don't think it needs tracking for 77 as we are in RC week. There are in total 2510 crashes on the release channel over a year, most of them in 75/76. Currently we have about 70 crashes per day for this signature but the volume on beta is only a handful on the whole beta cycle so there is no indication that the situation is going to be bad for 77.

I am setting it as fix-optional for 77 as a potential ride along in case we have a dot release and a safe fix materializes in the meantime.

We should figure out what's up ASAP.

Assignee: nobody → jgilbert
Severity: -- → S1
Flags: needinfo?(jgilbert)
Priority: -- → P1
Flags: needinfo?(jbonisteel)
Severity: S1 → S2

:jgilbert is this still considered a P1?

Flags: needinfo?(jgilbert)
Severity: S2 → S3
Flags: needinfo?(jgilbert)
Priority: P1 → P3
QA Whiteboard: qa-not-actionable

Closing because no crashes reported for 12 weeks.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.