nautilus crashed with SIGSEGV in _int_malloc()

[Daniel Winzen]

I opened a folder on a NTFS filesystem and nautilus crashed while loading it.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: nautilus 1:3.6.3-0ubuntu5
ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
Uname: Linux 3.8.0-1-generic x86_64
ApportVersion: 2.8-0ubuntu2
Architecture: amd64
Date: Fri Jan 25 17:45:02 2013
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'1116x685+343+150'"
InstallationDate: Installed on 2012-04-03 (296 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120403)
MarkForUpload: True
ProcCmdline: nautilus -n
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f6c39e6ec96: mov 0x10(%r14),%r8
 PC (0x7f6c39e6ec96) ok
 source "0x10(%r14)" (0x1e11e4953f6002c) not located in a known VMA region (needed readable region)!
 destination "%r8" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 malloc () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
Title: nautilus crashed with SIGSEGV in malloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 _int_malloc (av=av@entry=0x7f6c3a1aa740 <main_arena>, bytes=bytes@entry=36) at malloc.c:3352
 __GI___libc_malloc (bytes=36) at malloc.c:2858
 read_packet (c=0xdb0470) at ../../src/xcb_in.c:168
 _xcb_in_read (c=c@entry=0xdb0470) at ../../src/xcb_in.c:662
 poll_for_next_event (c=0xdb0470, queued=queued@entry=0) at ../../src/xcb_in.c:533

[Ads20000 (ads20000)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 1105293

and any other logs that are relevant for this particular issue.

[Launchpad Janitor (janitor)]

[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.]