From owner-freebsd-gecko@freebsd.org Tue Jan 2 07:08:51 2018 Return-Path: Delivered-To: freebsd-gecko@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 9D395EB7B04 for ; Tue, 2 Jan 2018 07:08:51 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 8CAD272E07 for ; Tue, 2 Jan 2018 07:08:51 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 8C156EB7B03; Tue, 2 Jan 2018 07:08:51 +0000 (UTC) Delivered-To: gecko@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 8BC73EB7B02 for ; Tue, 2 Jan 2018 07:08:51 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6DB8672E06; Tue, 2 Jan 2018 07:08:51 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1354) id 87D0187A9; Tue, 2 Jan 2018 07:08:50 +0000 (UTC) From: Jan Beich To: Kevin Oberman Cc: gecko@freebsd.org Subject: Re: Firefox 57 is eating my system References: Date: Tue, 02 Jan 2018 08:08:44 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-gecko@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Gecko Rendering Engine issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jan 2018 07:08:51 -0000 Kevin Oberman writes: > Any hope for mozjemalloc? At this time I need to shutdown and restart > Firefox often and might be as bad as Chromium for memory use. > > i know that the malloc issue is at least a significant issue in memory use. > Is there a real intractable issue with getting the mozjemalloc working on > FreeBSD or is it just a matter of developer time? "developer time" presumes there're developers. I'm just an #ifdef monkey. Porting a jemalloc fork requires understanding how jemalloc bootstraps. Old jemalloc (from FreeBSD 7-9) used spinlocks, no clue about the new one. mozjemalloc complicates this by code churn each Firefox release. To my knowledge, no one is working on porting mozjemalloc, so feel free to send patches. I can only help with build glue. > While I'm at it, what about OSS? Not nearly as critical, but would be nice. OSS in its unmaintained state is there for years as files/patch-bug1021761. pkg-message nowadays documents how to switch audio backend. Firefox build is simply broken without either ALSA, PULSEAUDIO or SNDIO, so you can't have pure OSS setup. To my knowledge, no one is working on finshing OSS support, so feel free to send patches. I can only help with build glue.