Closed Bug 39344 Opened 26 years ago Closed 26 years ago

mac verification build fails - out of memory

Categories

(SeaMonkey :: Build Config, defect, P1)

PowerPC
Mac System 8.6

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: granrosebugs, Assigned: jj.enser)

Details

(Whiteboard: [dogfood+])

Verification builds failed yesterday and today with the same error: ### Building "FastFreddy:Mozilla Tree:mozilla:js:macbuild:JavaScript.mcp" (Mon May 15 12:22:11 2000) Error : ### Error: Out of memory ### ### Build failed. --- I'm stumped. No verification build means no testing, means mac gets even further behind...
Priority: P3 → P1
Target Milestone: --- → M16
Putting on [dogfood+] radar.
Keywords: dogfood
Whiteboard: [dogfood+]
I just bumped up CodeWarrior's memory partiton from 28MB to 32MB, but this might not be enough. System momery (largest unused block) is now 100 MB which could be less than what the IDE needs to compile Javascript.mcp We should find out soon enough, with the verification cycle currently in progress. If the problem persists, next thing to try is to turn VM on with 300 or 400 MB. If VM is really not recommended on the verification build machine, we'll have to order additional RAM for the G4.
Status: NEW → ASSIGNED
thanks, jj! unfortunately, it failed again this morning with the same error. Would any of the Mac DIMMs I found a while back be usable in the verification system or do we have to order new ones? cc leaf since I forgot to do so yesterday.
Why did this just start to break? Is there a protocol change in how the machine is being run? Is it no longer being rebooted between builds or something?
No, we still reboot between builds. I didn't change anything about how the release builds are done, but JJ might have (though i doubt he did so this weekend). I turned VM on, i think that's what solved the problem (i was just informed that CW uses temp memory for most of it's work, which explains why increasing the mem partition didn't help). When the tree reopens today i'll try throttling down the mem partition for CW, and see if i can get away with turning off VM for faster build times.
jon: unfortunately, all the old dimms we have won't work in a G4. You need specific dimms (for b&w G3 or G4, not sure about the exact specs.) simon: I don't think anything changed since last Friday, when the automation still worked. My interpretation is that we progressively need more and more ram to do a build, and everything works fine until we reach the limit, and then it fails ;-) We should find out which machine can build optimized with 256 MB of RAM and no VM, to see if this config is always failing or not. I don't remember the config of retentive (clbr opt tinderbox) leaf: if you turn VM on, set it to more than 257MB (probably the default)
since leaf has a workaround, lowering severity to major.
Severity: blocker → major
this is fixed. marking fixed to save jj having to dial in from france...
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
verified.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.