From owner-freebsd-gecko@freebsd.org Wed Jan 3 21:09:43 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 1AE64EAF82C for ; Wed, 3 Jan 2018 21:09:43 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id E8D7566B88 for ; Wed, 3 Jan 2018 21:09:42 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id E1C0BEAF82A; Wed, 3 Jan 2018 21:09:42 +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 E160AEAF829 for ; Wed, 3 Jan 2018 21:09:42 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ua0-x229.google.com (mail-ua0-x229.google.com [IPv6:2607:f8b0:400c:c08::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9DC4966B86; Wed, 3 Jan 2018 21:09:42 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-ua0-x229.google.com with SMTP id l12so1892548uaa.10; Wed, 03 Jan 2018 13:09:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=1SKDnsKWLS4oqAa2x2x14tS8eQ+RM4rR2yZEz2azAtw=; b=N91678C+MQZu7O3Z1IU1qziBlc5WLLYZV1nGu9dBZOKvTvZh2nVFAFNn86XL93LcDa 4iNXjSD9X/8e2upuZCo/VqRwPDBamtW5eZc45KbKIK74Wcqryffyr/ZxYKILGVS33fQ6 hTEv01x148cgyRESDbFI63cNuCQl+jNYBlUnmUJxKSelqICqVQix+PdCDmgsMCc6ZfYz tOIQpd9qWp8J271b/+dQYe7hooHC0glWeL2SLF+IK5+gY4IvVSzCUgy4r/2AHlNVL+Gl nB2wSX++SXDoYA/Rpbt9YcJh8VfL3cc+DeLePdUvtg8l6m9N1k3v4ltFaJGzHcFgRZLa l17Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=1SKDnsKWLS4oqAa2x2x14tS8eQ+RM4rR2yZEz2azAtw=; b=rf0ZdnJTUuo+yFYSgmeHIRhj9ElCyAbK56NeKgfoH22uUN88N8GTyoebx/vdE0BsfM rCMF8VaQv/6udziMHhjXbz8wCzup7d86CjOv4+jdY+mhi+6HzcGOeq4D2UGELgy8panL YV6kJ00PdR0X9yTYnqHQf9LvSqgfjJ0LaNP2NWASEZuYzzp5EPPn3UAAzZazxGT7eb0Z v+fSSPnpcLhZ4orh5kxjvslVZh491bFa8n3KX69kYSPpaYdyMbWJaY0p8WxihbbnC9c5 d1hgfLA4aGr2dSTbggvXqeHvt8CwOxZTsifcVoUg+/0TyjBb6BjNFEq1WqgoerAB3lGD xPNA== X-Gm-Message-State: AKGB3mJX/xIMZIz5TtxrNw06Qo92tgmS+aKoBMEGrLF49ScaVYGbKul/ EWccqskDg1UwCi4KZjZpnnk3BlECVaGdtaQaY0kVjhCg X-Google-Smtp-Source: ACJfBovzk3IPeDp+qC3xC/vhITmjZQBjPdXM9XwgvJFnTYfzWLj7NchZWgKYZO88mS13yZvXGwZbrra0F091Ny/Swpc= X-Received: by 10.176.49.144 with SMTP id d16mr2809427uan.3.1515013781179; Wed, 03 Jan 2018 13:09:41 -0800 (PST) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 10.103.147.156 with HTTP; Wed, 3 Jan 2018 13:09:40 -0800 (PST) In-Reply-To: References: From: Kevin Oberman Date: Wed, 3 Jan 2018 13:09:40 -0800 X-Google-Sender-Auth: ZYpdN8OTo-bXT-j1854_1_LE6Ac Message-ID: Subject: Re: Firefox 57 is eating my system To: Jan Beich Cc: gecko@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Wed, 03 Jan 2018 21:09:43 -0000 On Mon, Jan 1, 2018 at 11:08 PM, Jan Beich wrote: > 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. > Thanks, Jan. Much as I suspected. I was hoping for hope for mozjemalloc. OSS is exactly how I expected to find it. I do think I'll try moving from ALSA to SNDIO. It looks like a somewhat cleaner system. I have not done serious coding in C in many years, so I doubt I can be of much use. Like you, I can only help with build glue. Right now, getting avidemux 2.7 working is a higher priority for what I can do and I've been bashing my head on a wall for a while now trying to track down the failing configuration code that does not like our NASM. I've grepped thought sources, unpacked embedded tar and zip files and grepped them, then done the same for bzgrep and its kin. It's in there, somewhere. Again, thanks for your work on various FreeBSD ports, especially Mesa and related stuff. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683