Bug 696952

Summary: [abrt] nautilus-2.32.2.1-2.fc14: g_slice_free1: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Yann Droneaud <yann>
Component: nautilusAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: ccecchi, tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:a82f2c5f8ce2a0c35d1daf5f9087d0d439be1493
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-30 13:24:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Yann Droneaud 2011-04-15 11:43:07 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 46346 bytes
cmdline: nautilus
component: nautilus
Attached file: coredump, 66916352 bytes
crash_function: g_slice_free1
executable: /usr/bin/nautilus
kernel: 2.6.35.12-88.fc14.x86_64
package: nautilus-2.32.2.1-2.fc14
rating: 4
reason: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1302862591
uid: 500

How to reproduce
-----
1. Don't know
2.
3.

Comment 1 Yann Droneaud 2011-04-15 11:43:10 UTC
Created attachment 492352 [details]
File: backtrace

Comment 2 Yann Droneaud 2011-04-15 11:46:30 UTC
I'm running my system with those environment variables set:

G_DEBUG=resident-modules,gc-friendly
G_SLICE=always-malloc,debug-blocks

.xsession-errors contains:

GSlice: MemChecker: attempt to release non-allocated block: 0xe598b0 size=24

Comment 3 Yann Droneaud 2011-04-15 11:48:05 UTC
It really looks like bug 681295

Comment 4 abrt-bot 2012-03-30 13:24:41 UTC
Backtrace analysis found this bug to be similar to bug #708643, closing as duplicate.

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 708643 ***