gala crashed with SIGSEGV in send_frame_messages_timeout()

Bug #1422105 reported by Sergey Peshkov
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Gala
New
Undecided
Unassigned

Bug Description

This happens periodically at random moments in time, I can't figure out what actually is causing it. But as I remember the last thing I did before Gala crashed was using Chrome and typing some info into textbox, then everything freezed for like 15 seconds and the Apport window appeared.

ProblemType: Crash
DistroRelease: elementary OS 0.3
Package: gala 0.1.0~r431+pkg29~ubuntu0.3.1 [origin: LP-PPA-elementary-os-daily]
ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
Uname: Linux 3.13.0-45-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CrashDB: gala
CurrentDesktop: Pantheon
Date: Sun Feb 15 14:33:35 2015
ExecutablePath: /usr/bin/gala
GsettingsChanges:

InstallationDate: Installed on 2015-02-10 (4 days ago)
InstallationMedia: elementary OS 0.3 "Freya" - Daily amd64 (20150208)
ProcCmdline: gala
SegvAnalysis:
 Segfault happened at: 0x7fcf0681d08a: mov 0x1c0(%rax),%rax
 PC (0x7fcf0681d08a) ok
 source "0x1c0(%rax)" (0x000001c0) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gala
StacktraceTop:
 ?? () from /usr/lib/libmutter.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gala crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Sergey Peshkov (serge1peshcoff) wrote :
Revision history for this message
Sergey Peshkov (serge1peshcoff) wrote :

BTW, forget to mention I'm using Freya Beta 2, but I've experienced this on Freya Beta 1 also.

information type: Private → Public
Revision history for this message
Sergey Peshkov (serge1peshcoff) wrote :

I've also experienced this bug when switching keyboard layout via Ctrl-Space (that's strange, but I didn't do anything except that, and it froze just right after I changed the layout).

Revision history for this message
Sergey "Shnatsel" Davidoff (shnatsel) wrote :

StacktraceTop:
 send_frame_messages_timeout (data=0x4141bb0, data@entry=<error reading variable: value has been optimized out>) at compositor/meta-window-actor.c:798
 g_timeout_dispatch (source=0x36e7f80, callback=<optimized out>, user_data=<optimized out>) at /build/buildd/glib2.0-2.42.1/./glib/gmain.c:4520
 g_main_dispatch (context=0xb064f0) at /build/buildd/glib2.0-2.42.1/./glib/gmain.c:3111
 g_main_context_dispatch (context=context@entry=0xb064f0) at /build/buildd/glib2.0-2.42.1/./glib/gmain.c:3710
 g_main_context_iterate (context=0xb064f0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at /build/buildd/glib2.0-2.42.1/./glib/gmain.c:3781

Revision history for this message
Sergey "Shnatsel" Davidoff (shnatsel) wrote : Stacktrace.txt
Revision history for this message
Sergey "Shnatsel" Davidoff (shnatsel) wrote : ThreadStacktrace.txt
summary: - gala crashed with SIGSEGV in g_main_context_dispatch()
+ gala crashed with SIGSEGV in send_frame_messages_timeout()
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.