tracker-extract crashed with signal 5 in g_malloc()

Bug #1174279 reported by Laurent Bonnaud
126
This bug affects 30 people
Affects Status Importance Assigned to Milestone
Ubuntu GNOME
Confirmed
Undecided
Unassigned

Bug Description

tracker-extract crashed while reindexing my homedir. I will try to find and upload the concerned file...

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: tracker-extract 0.16.0-2ubuntu1~ubuntu13.04.1 [origin: LP-PPA-gnome3-team-gnome3]
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
Date: Mon Apr 29 13:09:53 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/tracker/tracker-extract
InstallationDate: Installed on 2013-04-27 (1 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcCmdline: /usr/libexec/tracker-extract
Signal: 5
SourcePackage: tracker
StacktraceTop:
 g_malloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
 gst_buffer_new_allocate () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstpnm.so
Title: tracker-extract crashed with signal 5 in g_malloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Laurent Bonnaud (laurent-bonnaud) wrote :
information type: Private → Public
Revision history for this message
Laurent Bonnaud (laurent-bonnaud) wrote :

This bug is not a real crash. Tracker probably killed one of its child processes because it was using too much CPU or RAM.
Unfortunately the crash info does not contain any indication of which in my homedir file caused the problem.

Tim Lunn (darkxst)
Changed in ubuntu-gnome:
status: New → Confirmed
Revision history for this message
Juan G. Kings (juan-seo) wrote :

I agree with Laurent, I didn't experience a full on crash.

the screen may have locked for about 30seconds to a minute. but then came back.

im running 8 Gbs that may be why. also its an intel i5..

Good luck fixing this bug

Revision history for this message
heriberto (hmondragonr) wrote :

No se porque Pasa esto?

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.