Bug 889770 - [abrt] gnome-shell-3.6.2-3.fc18: Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV)
Summary: [abrt] gnome-shell-3.6.2-3.fc18: Process /usr/bin/gnome-shell was killed by s...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:9c7e3cdb4d14858feea73348c92...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-23 12:31 UTC by Jan Teichmann
Modified: 2013-01-10 09:06 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-01-10 09:06:45 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (171.59 KB, text/plain)
2012-12-23 12:31 UTC, Jan Teichmann 		no flags Details
File: cgroup (126 bytes, text/plain)
2012-12-23 12:31 UTC, Jan Teichmann 		no flags Details
File: core_backtrace (8.25 KB, text/plain)
2012-12-23 12:31 UTC, Jan Teichmann 		no flags Details
File: dso_list (22.86 KB, text/plain)
2012-12-23 12:31 UTC, Jan Teichmann 		no flags Details
File: environ (1.18 KB, text/plain)
2012-12-23 12:31 UTC, Jan Teichmann 		no flags Details
File: limits (1.29 KB, text/plain)
2012-12-23 12:32 UTC, Jan Teichmann 		no flags Details
File: maps (97.66 KB, text/plain)
2012-12-23 12:32 UTC, Jan Teichmann 		no flags Details
File: open_fds (1.13 KB, text/plain)
2012-12-23 12:32 UTC, Jan Teichmann 		no flags Details
File: proc_pid_status (923 bytes, text/plain)
2012-12-23 12:32 UTC, Jan Teichmann 		no flags Details
File: var_log_messages (403 bytes, text/plain)
2012-12-23 12:32 UTC, Jan Teichmann 		no flags Details
View All

Description Jan Teichmann 2012-12-23 12:31:39 UTC 
Version-Release number of selected component:
gnome-shell-3.6.2-3.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
executable:     /usr/bin/gnome-shell
kernel:         3.6.10-4.fc18.x86_64
remote_result:  803147
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 ??
 #1 clutter_actor_dispose at ./clutter-actor.c:5752
 #3 clutter_actor_destroy at ./clutter-actor.c:8376
 #4 ffi_call_unix64 at ../src/x86/unix64.S:75
 #5 ffi_call at ../src/x86/ffi64.c:486
 #6 gjs_invoke_c_function at gi/function.c:893
 #7 function_call at gi/function.c:1204
 #8 CallJSNative at jscntxtinlines.h:701
 #9 js::Invoke at jsinterp.cpp:696
 #10 js::Interpret at jsinterp.cpp:4810
Comment 1 Jan Teichmann 2012-12-23 12:31:46 UTC 
Created attachment 668010 [details]
File: backtrace
Comment 2 Jan Teichmann 2012-12-23 12:31:48 UTC 
Created attachment 668011 [details]
File: cgroup
Comment 3 Jan Teichmann 2012-12-23 12:31:50 UTC 
Created attachment 668012 [details]
File: core_backtrace
Comment 4 Jan Teichmann 2012-12-23 12:31:56 UTC 
Created attachment 668013 [details]
File: dso_list
Comment 5 Jan Teichmann 2012-12-23 12:31:58 UTC 
Created attachment 668014 [details]
File: environ
Comment 6 Jan Teichmann 2012-12-23 12:32:00 UTC 
Created attachment 668015 [details]
File: limits
Comment 7 Jan Teichmann 2012-12-23 12:32:03 UTC 
Created attachment 668016 [details]
File: maps
Comment 8 Jan Teichmann 2012-12-23 12:32:05 UTC 
Created attachment 668017 [details]
File: open_fds
Comment 9 Jan Teichmann 2012-12-23 12:32:07 UTC 
Created attachment 668018 [details]
File: proc_pid_status
Comment 10 Jan Teichmann 2012-12-23 12:32:09 UTC 
Created attachment 668019 [details]
File: var_log_messages
Comment 11 Jan Teichmann 2013-01-10 09:06:45 UTC 
I noticed more strange memory corruption in other programs recently and as it turned out I had a defective RAM module. Effects were very random and rare but could be the cause of most memory corruption I lately reported. I assumed it is related to the beta state of F18 so I didnt suspect the RAM at first but MemTest found a small address range with errors.
I am extremely sorry for taking up your time hunting down bugs which are most likely not there. I decided to close my latest bug reports as I can not assure that the memory corruption was actually caused by the program rather than the defect RAM module.
Note You need to log in before you can comment on or make changes to this bug.