Bug 1247518

Summary:	firefox with gpu hwaccel and crash reports (empty?)
Product:	[Fedora] Fedora	Reporter:	lejeczek <peljasz>
Component:	firefox	Assignee:	Gecko Maintainer <gecko-bugs-nobody>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	22	CC:	d.bz-redhat, gecko-bugs-nobody, jhorak, pjasicek, stransky
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-20 09:04:16 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description lejeczek 2015-07-28 08:21:24 UTC

Description of problem:

having:
layers.acceleration.force-enabled
layers.offmainthreadcomposition.enabled

firefox crashes constantly and I send "crash reports" to Mozilla, but then I click for details there is nothing, empty field. So I wonder if these reports work in the first place?

Version-Release number of selected component (if applicable):

39.0

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Didier 2015-08-19 10:36:40 UTC

firefox-40.0-4.fc22.x86_64 (with layers.offmainthreadcomposition.enabled by default set to false) stops crashing (I am also experiencing the empty crash details pages) when package "libva-vdpau-driver" is uninstalled (cfr. bug #1219068 ?).

Comment 2 Martin Stransky 2015-08-20 09:04:16 UTC

Yes, 40.0-4 disables the OMTC. We're going to re-enable it in FF41.

Comment 3 lejeczek 2015-08-20 11:39:28 UTC

but how about those internal crash reports to Mozilla, does this even work? Like I said, field with details is each time empty.

Comment 4 Martin Stransky 2015-08-20 11:43:35 UTC

Those reports are malformed because of the corrupted memory.