From owner-freebsd-questions Thu Apr 30 09:43:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA05907 for freebsd-questions-outgoing; Thu, 30 Apr 1998 09:43:45 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from cerberus.partsnow.com (gatekeeper.partsnow.com [207.155.26.98] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA05895 for ; Thu, 30 Apr 1998 09:43:38 -0700 (PDT) (envelope-from don@partsnow.com) Received: (from bin@localhost) by cerberus.partsnow.com (8.8.5/8.6.9) id JAA11794 for ; Thu, 30 Apr 1998 09:42:50 -0700 (PDT) X-Authentication-Warning: cerberus.partsnow.com: bin set sender to using -f Received: from wildeweb(192.168.100.10) by cerberus.partsnow.com via smap (V2.0) id xma011788; Thu, 30 Apr 98 09:42:32 -0700 Message-ID: <3548A9E3.DE4AD109@partsnow.com> Date: Thu, 30 Apr 1998 09:42:11 -0700 From: Don Wilde Reply-To: don@partsnow.com Organization: Soligen, Incorporated X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: freebsd-questions@FreeBSD.ORG Subject: xscreensaver programs die? Content-Type: multipart/mixed; boundary="------------AED9D66FA334BBFBD25A7701" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------AED9D66FA334BBFBD25A7701 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit On my development PC with X, I use fvwm on top of X as included with 2.2.5. It was a clean install, not an upgrade. A number of the xscreensaver 2.7 programs crash and leave an 'I died' message on the screen. I'm running S3V on a Number Nine 331 card, 1024x1280 at 8bpp. Is this peculiar to my setup, is it now fixed in 2.2.6 (haven't gotten that far!), or is there a known issue that needs to be addressed. It doesn't bother me except in that it's messy, and it doesn't impact the rest of my machine or lock anything up (Thank you, -core and XFree86!!!). See the attachment for examples. -- oooOOO O O O o * * * * * * o ___ _________ _________ ________ _________ _________ ___==_ V_=_=_DW ===--- Don Wilde [don@PartsNow.com] [http://www.PartsNow.com ] /oo0000oo-oo--oo-ooo---ooo-ooo---ooo-ooo--ooo-ooo---ooo-ooo---ooo-oo--oo  --------------AED9D66FA334BBFBD25A7701 Content-Type: text/plain; charset=us-ascii; name="temp" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="temp" This is the normal failure (from '/var/log/messages'): Mar 25 20:10:05 WildeWeb /kernel: pid 520 (swirl), uid 65534: exited on signal 8 Mar 25 21:40:40 WildeWeb /kernel: pid 686 (spiral), uid 65534: exited on signal 8 Mar 25 22:40:53 WildeWeb /kernel: pid 733 (starfish), uid 65534: exited on signal 8 This is the extreme: Apr 3 02:08:10 WildeWeb /kernel: pid 3731 (starfish), uid 65534: exited on signal 8 Apr 3 03:20:26 WildeWeb /kernel: pid 3792 (flame), uid 65534: exited on signal 8 Apr 3 14:08:57 WildeWeb /kernel: pid 4326 (flame), uid 65534: exited on signal 8 Apr 3 20:54:11 WildeWeb /kernel: pid 4647 (attraction), uid 65534: exited on signal 8 Apr 4 03:35:51 WildeWeb /kernel: swap_pager: out of swap space Apr 4 03:40:03 WildeWeb /kernel: pid 5958 (sh), uid 0, was killed: out of swap space Apr 4 03:45:02 WildeWeb /kernel: pid 5960 (sh), uid 0, was killed: out of swap space Apr 4 03:45:41 WildeWeb /kernel: pid 5961 (julia), uid 65534: exited on signal 11 Apr 4 03:50:02 WildeWeb /kernel: pid 5964 (sh), uid 0, was killed: out of swap space Apr 4 03:55:03 WildeWeb /kernel: pid 5966 (sh), uid 0, was killed: out of swap space Apr 4 03:55:43 WildeWeb /kernel: pid 5967 (lightning), uid 65534: exited on signal 11 Apr 4 04:00:03 WildeWeb /kernel: pid 5970 (sh), uid 0, was killed: out of swap space Apr 4 04:00:04 WildeWeb /kernel: pid 5971 (sh), uid 0, was killed: out of swap space Apr 4 04:01:03 WildeWeb /kernel: pid 5973 (sh), uid 0, was killed: out of swap space Apr 4 04:05:03 WildeWeb /kernel: pid 5975 (sh), uid 0, was killed: out of swap space Somebody's got a leak, eh? This machine has 32M of DRAM and two 64M swap partitions. --------------AED9D66FA334BBFBD25A7701-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message