On Fri, Feb 05, 2021 at 04:42:26PM -0600, Matt Connell (Gmail) wrote > On Fri, 2021-02-05 at 13:24 -0500, Walter Dnes wrote: > > I'll have to take that back. It happened again, and I was not > > fiddling with pstop/pcont. The common element seems to be that I was > > compiling Pale Moon 29.0 each time it crashed. A machine with 8 gigs of > > ram, and 598 of 905 gigs free diskspace should not have resource issues. > > I contest this claim. 8GB is pretty scant for something as large and > complex as a modern browser. Have you built this before on the same > machine?
See http://www.palemoon.org/releasenotes.shtml My previous successful build was 28.17.0 which was released December 18th. Note: Chrome and Firefox seem to bump the major release number "just because". The Pale Moon devs use all 3 digits. E.g. an isolated bugfix has just been released as 29.0.1. When the major release number on Pale Moon is incremented, there are big changes "under the hood", so increased requirements are a possibility going from version 28.17 to 29.0. There's also ongoing work on "de-unifying the sources" https://forum.palemoon.org/viewtopic.php?f=62&t=24296 The thread starts off with the question "Is it expected that Pale Moon compilation time has almost doubled after de-unifying the sources?". To which the head honcho replies... > That was only de-unifying /dom -- more will follow. > > And yes, if your aren't on a particularly powerful machine with > a fast drive, it can impact your compilation time significantly. I have a relatively new 16-gig machine (October) that I'll try it on. -- Walter Dnes <[email protected]> I don't run "desktop environments"; I run useful applications
