Date: Wed, 3 Jan 2018 13:09:40 -0800 From: Kevin Oberman <rkoberman@gmail.com> To: Jan Beich <jbeich@freebsd.org> Cc: gecko@freebsd.org Subject: Re: Firefox 57 is eating my system Message-ID: <CAN6yY1vcEPE76Syn4bsFDe1MPyqFg0K%2BPQHrcpzDR9qrE7u_UA@mail.gmail.com> In-Reply-To: <mv1w-u48z-wny@FreeBSD.org> References: <CAN6yY1v_R__0E2gXt7L9C9_w2o0ssjYWN3KG7szxUZ=BJpcsvw@mail.gmail.com> <mv1w-u48z-wny@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 1, 2018 at 11:08 PM, Jan Beich <jbeich@freebsd.org> wrote: > Kevin Oberman <rkoberman@gmail.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1vcEPE76Syn4bsFDe1MPyqFg0K%2BPQHrcpzDR9qrE7u_UA>