gimp-2.8 SIGSEGV in g_slice_alloc() while idling

[Moses Moore]

I often leave gimp minimized in the background, with no image loaded.
After upgrading to Ubuntu 13.10, three times now I've had it crash while minimzed.

The apport report says "gimp-2.8 crashed with SIGSEGV in g_slice_alloc()" and "reading unknown VMA".

I have trouble reproducing the error because it only happens when I'm *not* using gimp.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: gimp 2.8.6-1ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
Date: Sun Oct 27 11:55:29 2013
InstallationDate: Installed on 2013-06-08 (141 days ago)
InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1)
MarkForUpload: True
SourcePackage: gimp
UpgradeStatus: Upgraded to saucy on 2013-10-18 (8 days ago)

[Moses Moore (moses-mozai)]

forgot I already filed this bug; happens more than once a week now.

[Moses Moore (moses-mozai)]

I don't know how to get apport to give me a copy of the crash info, instead of sending off into the aether and vanishing. I can look at the text on-screen and transcribe it here.

SegvAnalysis:
  Segfault happened at: 0xb6a4db2e <g_slice_alloc+158>: mov (%edit),%edx
  PC(0xb6a4db2e) ok
  source "(%edi)" (0x503b276e) not located in a known VMA region (needed readable region!)
  destination "%edx" ok
  Stack memory exhasted (SP below stack segment)
SegvReason:
  reading unknown VMA
StackTraceTop:
  g_slice_alloc() from /lib/i386-linux-gnu/libglib-2.0.so.0
  g_slice_allo0() from /lib/i386-linux-gnu/libglib-2.0.so.0
  g_type_create_instance() from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  ??() from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  g_object_newv() from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0