Description of problem: Did install from rawhide last night on my f10 beta system, got this during install: Updating : openoffice.org-voikko [ 89/203] terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Version-Release number of selected component (if applicable): openoffice.org-voikko-3.0-2.fc10.x86_64 How reproducible: I only tried it the one time. Steps to Reproduce: 1.yum update 2. 3. Actual results: bad_alloc exception Expected results: no errors during install Additional info:
This is quite hard to debug. The exception means something went wrong with allocating memory. When installing openoffice.org-voikko, rpm runs an OpenOffice.org tool called unopkg, I presume that's where the exception comes from (and that's why I'm CCing Caolan). For what it's worth, I couldn't reproduce the error on my i386 Rawhide virtual machine.
Hmm, I have no idea either, but I suspect there might be a connection to #461763 Feel free to mark it as a duplicate along the lines of super-suspicious failure during a big yum transaction which fails to happen in isolation. I'm suspicious as to whether it is OOo which is doing something crazy, or of e.g. the python garbage collector hasn't had a chance to run during transactions and eats all available memory. Though that's just a crazy theory. I would be interested in knowing what memory exists on the box that failed ?
There is two gig of physical memory on the machine where this happened and an 8 gig swap area. The messages also scrolled past at normal speed, nothing seemed like it had bogged down due to trashing or anything. I suppose rather than using up all memory, it might have had some corrupted memory location cause it to request something like 200 gig and have that request rejected as ridiculous without first going to all the trouble of eating all memory and bogging down the machine.
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Let's call it a duplicate of 461763. Not that that helps fix it, but hasn't been seen again so... *** This bug has been marked as a duplicate of bug 461763 ***