← Back to team overview

linux-traipu team mailing list archive

[Bug 1378627] Re: chromium-browser crashed with SIGSEGV

 

Launchpad has imported 14 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1123691.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2014-07-28T01:17:24+00:00 LUIS wrote:

Version-Release number of selected component:
cheese-3.10.2-1.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        cheese
crash_function: get_stencil_miptree
executable:     /usr/bin/cheese
kernel:         3.15.4-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 get_stencil_miptree at brw_misc_state.c:257
 #1 brw_workaround_depthstencil_alignment at brw_misc_state.c:273
 #2 brw_clear at brw_clear.c:231
 #3 cogl_framebuffer_clear4f at ./cogl-framebuffer.c:374
 #4 cogl_framebuffer_clear at ./cogl-framebuffer.c:442
 #5 cogl_clear at ./cogl.c:87
 #6 _clutter_stage_do_pick at ./clutter-stage.c:1583
 #7 _clutter_input_device_update at ./clutter-input-device.c:899
 #8 _clutter_process_event_details at ./clutter-main.c:2453
 #9 _clutter_process_event at ./clutter-main.c:2777

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1378627/comments/1

------------------------------------------------------------------------
On 2014-07-28T01:17:29+00:00 LUIS wrote:

Created attachment 921613
File: backtrace

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1378627/comments/2

------------------------------------------------------------------------
On 2014-07-28T01:17:30+00:00 LUIS wrote:

Created attachment 921614
File: cgroup

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1378627/comments/3

------------------------------------------------------------------------
On 2014-07-28T01:17:31+00:00 LUIS wrote:

Created attachment 921615
File: core_backtrace

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1378627/comments/4

------------------------------------------------------------------------
On 2014-07-28T01:17:33+00:00 LUIS wrote:

Created attachment 921616
File: dso_list

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1378627/comments/5

------------------------------------------------------------------------
On 2014-07-28T01:17:34+00:00 LUIS wrote:

Created attachment 921617
File: environ

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1378627/comments/6

------------------------------------------------------------------------
On 2014-07-28T01:17:35+00:00 LUIS wrote:

Created attachment 921618
File: exploitable

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1378627/comments/7

------------------------------------------------------------------------
On 2014-07-28T01:17:36+00:00 LUIS wrote:

Created attachment 921619
File: limits

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1378627/comments/8

------------------------------------------------------------------------
On 2014-07-28T01:17:40+00:00 LUIS wrote:

Created attachment 921620
File: maps

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1378627/comments/9

------------------------------------------------------------------------
On 2014-07-28T01:17:41+00:00 LUIS wrote:

Created attachment 921621
File: open_fds

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1378627/comments/10

------------------------------------------------------------------------
On 2014-07-28T01:17:42+00:00 LUIS wrote:

Created attachment 921622
File: proc_pid_status

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1378627/comments/11

------------------------------------------------------------------------
On 2014-07-28T01:17:43+00:00 LUIS wrote:

Created attachment 921623
File: var_log_messages

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1378627/comments/12

------------------------------------------------------------------------
On 2015-05-29T12:29:41+00:00 Fedora wrote:

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1378627/comments/43

------------------------------------------------------------------------
On 2015-06-29T21:48:24+00:00 Fedora wrote:

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1378627/comments/44


** Changed in: chromium-browser (Fedora)
       Status: Unknown => Won't Fix

** Changed in: chromium-browser (Fedora)
   Importance: Unknown => Undecided

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/1378627

Title:
  chromium-browser crashed with SIGSEGV

Status in Chromium Browser:
  Unknown
Status in Mesa:
  Won't Fix
Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser package in Debian:
  Fix Released
Status in chromium-browser package in Fedora:
  Won't Fix

Bug description:
  No idea what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: chromium-browser 37.0.2062.94-0ubuntu1~pkg1065
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  Uname: Linux 3.16.0-21-generic x86_64
  ApportVersion: 2.14.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Wed Oct  8 07:12:48 2014
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2013-12-22 (289 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131221)
  ProcCmdline: chromium-browser\ --type=gpu-process\ --channel=3043.0.199670400\ --supports-dual-gpus=false\ --gpu-driver-bug-workarounds=1,11,15\ --disable-accelerated-video-decode\ --gpu-vendor-id=0x8086\ --gpu-device-id=0x0126\ --gpu-driver-vendor\ --gpu-driver-versi
  SegvAnalysis:
   Segfault happened at: 0x7fc0e6b1963f:	mov    0x1f8(%rax),%r15
   PC (0x7fc0e6b1963f) ok
   source "0x1f8(%rax)" (0x000001f8) not located in a known VMA region (needed readable region)!
   destination "%r15" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: chromium-browser
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/chromium-browser/libs/libgpu.so
   ?? () from /usr/lib/chromium-browser/libs/libcontent.so
   ?? () from /usr/lib/chromium-browser/libs/libcontent.so
  Title: chromium-browser crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare scanner sudo
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-09-14T18:16:36.315577

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1378627/+subscriptions