In message <CAGHfRMD=TCdQkJ54rKquDMj9z2jLOAK71p+thWg22Rb1K+-W0Q@mail.gmail.c om> , Ngie Cooper writes: > On Fri, May 5, 2017 at 4:43 PM, Cy Schubert <cy.schub...@komquats.com> wrote: > > ... > > > You have a bad DIMM. I had this same problem on my laptop but not on my > > servers downstairs. That suggested that since all four machines were > > running the same software the difference between them was hardware. > > Replacing the memory in my laptop made this problem go away. > > > > I have a question for you. Do you use ZFS? ZFS exercises memory quite > > aggressively. I also had this problem when I replaced my UFS filesystems > > with ZFS on my testbed many moons ago. It even suffered random kernel > > panics. Here again, replacing the memory resolved the issue. > > We need more information first before saying "bad hardware" -- in > particular, was the machine overtaxed, were the input files proper, > etc? > > I'm asking because clang has a number of bugs in bugzilla where the > host ran out of memory trying to compile things and clang didn't fail > gracefully when allocating memory, handling inputs, etc.
Running out of memory (physical RAM + swap) would invoke OOM. That would result in the process receiving SIGKILL not SIGSEGV. Per process limits? Possible. -- Cheers, Cy Schubert <cy.schub...@cschubert.com> FreeBSD UNIX: <c...@freebsd.org> Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
