tumblerd crashed with SIGSEGV in g_slice_alloc()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tumbler (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu
Trusty
2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center
thunar:
Installed: 1.6.3-1ubuntu4
Candidate: 1.6.3-1ubuntu4
3) What you expected to happen
No crash report
4) What happened instead
Crash report - occurred while navigating to a new directory.
Have had a problem like this previously, might be related to video thumbnails being loaded by ffmpegthumbnailer but this is just a theory. Haven't noticed this happening in directories which don't contain video files.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: tumbler 0.1.30-1ubuntu1
ProcVersionSign
Uname: Linux 3.13.0-20-generic x86_64
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Mon Mar 31 22:54:43 2014
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2012-12-26 (460 days ago)
InstallationMedia: Xubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3)
ProcCmdline: /usr/lib/
SegvAnalysis:
Segfault happened at: 0x7f4e5d3f8297 <g_slice_
PC (0x7f4e5d3f8297) ok
source "(%rbx)" (0x00000001) not located in a known VMA region (needed readable region)!
destination "%rax" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: tumbler
StacktraceTop:
g_slice_alloc () from /lib/x86_
g_slice_alloc0 () from /lib/x86_
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: tumblerd crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: Upgraded to trusty on 2014-03-13 (19 days ago)
UserGroups: adm audio cdrom dip kvm libvirtd lpadmin plugdev pulse pulse-access sambashare sudo vboxusers video
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1290041, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.