Bug 432368

Summary: building openoffice.org causes OOM
Product: [Fedora] Fedora Reporter: Karsten Hopp <karsten>
Component: openoffice.orgAssignee: Caolan McNamara <caolanm>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: rawhideCC: jnavrati
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-02-13 09:32:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
pstree output none

Description Karsten Hopp 2008-02-11 16:34:16 UTC 
Description of problem:
during a rebuild of openoffice.org I've noticed that one perl process per CPU
was created which in turn runs up to 1 compiler process per CPU. On a 16 CPU
machine this results in up to 256 gcc/g++ process which can bring down a machine
due to an out of memory situation. I've killed the build after it used up 8G
main memory and another 10G swap.

Version-Release number of selected component (if applicable):
openoffice.org-2.4.0-6.2.fc9



Steps to Reproduce:
1. Build openoffice.org on an SMP and watch p.e. with pstree how numcpu*numcpu
processes are created.
  

Additional info:
There should be only one compiler running  for each CPU, not numcpu compiler
process per CPU
Comment 1 Caolan McNamara 2008-02-13 09:32:19 UTC 
somewhat overly aggressive alright
Comment 2 Karsten Hopp 2008-02-13 13:09:50 UTC 
Created attachment 294768 [details]
pstree output
Comment 3 Karsten Hopp 2008-02-13 13:10:21 UTC 
... that's with 2.4.0-7.1.fc9