update-apt-xapian-index crashed with DatabaseLockError in __init__(): Unable to get write lock on /var/cache/apt-xapian-index/index.2: Couldn't fork: Cannot allocate memory

[Baskak]

no discernible scenario (apart from it's in a row of in crashes going on on my system, which i have even no time to submit)

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: apt-xapian-index 0.44ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
Date: Thu Sep 29 07:56:26 2011
ExecutablePath: /usr/sbin/update-apt-xapian-index
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/update-apt-xapian-index --quiet
ProcEnviron:
 PATH=(custom, no user)
 SHELL=/bin/sh
PythonArgs: ['/usr/sbin/update-apt-xapian-index', '--quiet']
SourcePackage: apt-xapian-index
Title: update-apt-xapian-index crashed with DatabaseLockError in __init__(): Unable to get write lock on /var/cache/apt-xapian-index/index.2: Couldn't fork: Cannot allocate memory
UpgradeStatus: Upgraded to oneiric on 2011-09-26 (2 days ago)
UserGroups:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #764701, 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.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.