Bug 1247518 - firefox with gpu hwaccel and crash reports (empty?)
Summary: firefox with gpu hwaccel and crash reports (empty?)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 22
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-28 08:21 UTC by lejeczek
Modified: 2015-08-20 11:43 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-08-20 09:04:16 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.