Bug 696952 - [abrt] nautilus-2.32.2.1-2.fc14: g_slice_free1: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT)
Summary: [abrt] nautilus-2.32.2.1-2.fc14: g_slice_free1: Process /usr/bin/nautilus was...
Keywords:
Status: CLOSED DUPLICATE of bug 708643
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:a82f2c5f8ce2a0c35d1daf5f908...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-15 11:43 UTC by Yann Droneaud
Modified: 2015-03-03 22:59 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-30 13:24:41 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (45.26 KB, text/plain)
2011-04-15 11:43 UTC, Yann Droneaud 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

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 ***
Note You need to log in before you can comment on or make changes to this bug.