crash in @0x0 |




Canvas: WebGL
3 years ago
5 months ago


(Reporter: Jukka Jylänki, Unassigned)



Firefox Tracking Flags

(Not tracked)


(Whiteboard: [gfx-noted], crash signature)



3 years ago
This bug was filed from the Socorro interface and is 
report bp-75b28ed7-9c26-4823-91a4-df16c2150629.

1. Visit

Observed: Firefox Nightly crashes.

Tested on


Samsung GT-I9500 (April 2013)
1080x1920 pixels display
Chipset: Samsung Exynos 5 Octa 5410
CPU: Quad-core 1.6 GHz Cortex-A15 & quad-core 1.2 GHz Cortex-A7
2GB of RAM
GPU: Imagination PowerVR SGX544MP3
	- OpenGL ES 2.0
Android 5.0.1
 - This is an important device because it is part of the Firefox Content Performance Program,
Firefox Nightly 41.0a1 (2015-06-29)

Comment 1

3 years ago
Did not crash on any of the following: SPARK, GIADA, MACBOOK_AIR_OSX, MACBOOK_AIR_WIN, MACBOOK_PRO_OSX, MACBOOK_PRO_WIN, MACMINI, MACPRO, NEXUS-4, NEXUS-5, NEXUS-10, SURFACE, WINDBOX, HASWELL, HPOMEN (see for hardware configuration details of these systems)
Whiteboard: [gfx-noted]
Mass resolving WFM: signature(s) hasn't(/haven't) reported in past 28 days.

Comment 3

2 years ago
Reopening, as the above is not a valid grounds for closing this bug.

This bug refers to a crash in the official WebGL conformance suite, which we test the official WebGL implementation functionality against. Closing bugs on statistical basis loses valuable information for developers. Closing a bug as WORKSFORME means you have tried the bug on the target hardware and OS on the latest browser, and can verify that the steps no longer produce the bug. We should not close bugs on statistical grounds unless they were opened on statistical grounds in the first place, or if they don't have clear steps to repro. This bug has a clear STR attached to it. Edwin, could you please revisit and reopen any bugs you have closed which either refer to an official conformance suite and/or have a clear steps to repro?
(In reply to Jukka Jylänki from comment #3)
> Reopening, as the above is not a valid grounds for closing this bug.

Could you please retest this and see if it's still valid?
Flags: needinfo?(jujjyl)

Comment 5

2 years ago
Retested today on the same Samsung GT-I9500 hardware as from comment 0, and the crash still occurs.
Flags: needinfo?(jujjyl)
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.