Ubuntu

crash with SIGSEGV in _pixman_image_get_solid()

Reported by João Santana on 2012-02-24
104
This bug affects 19 people
Affects Status Importance Assigned to Milestone
Unity
High
Unassigned
evince (Ubuntu)
Undecided
Unassigned
gnome-shell (Ubuntu)
High
Unassigned
pixman (Ubuntu)
High
Unassigned
unity (Ubuntu)
High
Unassigned

Bug Description

Random. Clicking on Ubuntu icon causes Compiz to crash.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity 5.4.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.92-0ubuntu1
Architecture: amd64
Date: Thu Feb 23 21:16:53 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.1)
ProcCmdline: compiz
SegvAnalysis:
 Segfault happened at: 0x7f6eb6dec300: add %al,(%rax)
 PC (0x7f6eb6dec300) in non-executable VMA region: 0x7f6eb65ff000-0x7f6eb6dff000 rw-p None
 source "%al" ok
 destination "(%rax)" (0xd836f778) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason:
 executing writable VMA None
 writing unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libpixman-1.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libpixman-1.so.0
 pixman_image_composite32 () from /usr/lib/x86_64-linux-gnu/libpixman-1.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

João Santana (joaosantana) wrote :
visibility: private → public

StacktraceTop:
 ?? ()
 _pixman_image_get_solid (imp=<optimized out>, image=<optimized out>, format=<optimized out>) at ../../pixman/pixman-image.c:892
 sse2_composite_over_n_8_8888 (imp=<optimized out>, info=<optimized out>) at ../../pixman/pixman-sse2.c:3132
 pixman_image_composite32 (op=<optimized out>, src=<optimized out>, mask=<optimized out>, dest=<optimized out>, src_x=22, src_y=26, mask_x=0, mask_y=0, dest_x=22, dest_y=26, width=13, height=17) at ../../pixman/pixman.c:712
 _composite_spans (closure=<optimized out>, dst=<optimized out>, dst_format=<optimized out>, op=CAIRO_OPERATOR_OVER, pattern=<optimized out>, dst_x=22, dst_y=0, extents=0x7f6eb6ded690, clip_region=0x0) at /build/buildd/cairo-1.10.2/src/cairo-image-surface.c:3510

Changed in unity (Ubuntu):
importance: Undecided → Medium
summary: - compiz crashed with SIGSEGV in pixman_image_composite32()
+ compiz crashed with SIGSEGV in _pixman_image_get_solid()
tags: removed: need-amd64-retrace

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in unity (Ubuntu):
status: New → Confirmed
Changed in gnome-shell (Ubuntu):
status: New → Confirmed
Changed in pixman (Ubuntu):
status: New → Confirmed
Changed in pixman (Ubuntu):
importance: Undecided → High
Changed in gnome-shell (Ubuntu):
importance: Undecided → High
Changed in unity (Ubuntu):
importance: Medium → High
Michal Hruby (mhr3) wrote :

Both Gnome Shell and Unity are loading icons in background threads, so it's likely a thread-unsafety issue in pixman.

Omer Akram (om26er) on 2012-06-18
Changed in unity:
status: New → Confirmed
importance: Undecided → High
bwat47 (bwat47) wrote :

still a problem with 12.04 LTS with all updates. never see the issue in 12.10 though. I saw it today on a fresh install of 12.04, fully updated. logged in, clicked dash, compiz crashed.

summary: - compiz crashed with SIGSEGV in _pixman_image_get_solid()
+ compiz crashed with SIGSEGV in _pixman_image_get_solid() from
+ gtk_icon_info_load_icon() from unity::dash::Style::Impl::Impl()

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in evince (Ubuntu):
status: New → Confirmed
summary: - compiz crashed with SIGSEGV in _pixman_image_get_solid() from
- gtk_icon_info_load_icon() from unity::dash::Style::Impl::Impl()
+ crash with SIGSEGV in _pixman_image_get_solid()
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers