> On 26 March 2015, at 18:02, Chris H <bsd-li...@bsdforge.com> wrote: > > On Thu, 26 Mar 2015 20:28:15 -0400 J David <j.david.li...@gmail.com> wrote > >> On Thu, Mar 26, 2015 at 8:25 PM, Chris H <bsd-li...@bsdforge.com> wrote: >>> As Kevin already noted; stopping firefox, and starting it again, >>> seems the only solution. >> >> The machines in questions are servers, they do not run Firefox or any >> GUI. And whatever is using the memory does not show up on ps or top. > Fair enough. I'm still getting caught up, on the thread. > > Maybe another "shot in the dark". But speaking of Servers. We > ran into trouble with a web server generating *enormous* error > logs -- a runaway script. The result was, even tho there was > far more than adequate space for the swelling log(s). Memory, > and eventually Swap usage, began to climb quite steadily. > > Like I said; maybe a shot in the dark. But just thought I'd > mention it.
I just encountered the same problem on a FreeBSD 8.2-RELEASE-p3 server today. Swap was at 100% and processes were being killed. I used ps ax and killed all the processes with W status that I could. Swap usage went down to 99%. This was a production server so was forced to reboot. After the reboot, the system came back up with the same process set and zero swap used. Shortly after that a core image appeared and the root filesystem was full. The core file was about 1 GB. However, none of my processes are anywhere near that. The specific process that was dumped is only about 140 lines of C code and doesn’t have any dynamic storage used, just a couple of short character strings and one integer. The binary file is 23KB. I couldn’t take time to run gdb on it as it was affecting production. _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
