From owner-freebsd-current@freebsd.org Tue Dec 20 21:29:28 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 18D16C889D4 for ; Tue, 20 Dec 2016 21:29:28 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EA34CFA4 for ; Tue, 20 Dec 2016 21:29:27 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id uBKLTKlm069814 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Tue, 20 Dec 2016 13:29:20 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id uBKLTKZN069813 for freebsd-current@freebsd.org; Tue, 20 Dec 2016 13:29:20 -0800 (PST) (envelope-from sgk) Date: Tue, 20 Dec 2016 13:29:20 -0800 From: Steve Kargl To: freebsd-current@freebsd.org Subject: unkillable firefox Message-ID: <20161220212920.GA69662@troutmask.apl.washington.edu> Reply-To: kargl@uw.edu MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.7.2 (2016-11-26) X-Mailman-Approved-At: Tue, 20 Dec 2016 22:36:23 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Dec 2016 21:29:28 -0000 Anyone know how to kill firefox? last pid: 69652; load averages: 0.49, 0.27, 0.24 up 1+02:40:06 13:16:02 126 processes: 1 running, 121 sleeping, 4 stopped CPU: 0.8% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle Mem: 2049M Active, 3739M Inact, 496M Laundry, 1365M Wired, 783M Buf, 239M Free Swap: 16G Total, 1772K Used, 16G Free PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU COMMAND 63902 kargl 40 0 3157M 2302M STOP 1 10:50 0.00% firefox{firefox} 63902 kargl -16 0 3157M 2302M STOP 2 5:46 0.00% firefox{Composit 16874 kargl 40 0 740M 330M STOP 1 0:07 0.00% firefox{firefox} 16874 kargl -16 0 740M 330M STOP 1 0:00 0.00% firefox{Composit It seems that firefox is wedged in the thread firefox{Compositor}, and slowly eating up memory. This is on an amd64 system at r310125 and latest firefox from ports. procstat suggests that its stuck in a vm sleep queue. % procstat -k 63902 PID TID COMM TDNAME KSTACK 63902 100504 firefox - mi_switch thread_suspend_switch thread_single exit1 sigexit postsig ast Xfast_syscall 63902 101494 firefox Compositor mi_switch sleepq_wait _sleep vm_page_busy_sleep vm_page_sleep_if_busy vm_fault_hold vm_fault trap_pfault trap calltrap -- Steve