[Bug 195678] mail/thunderbird does not build against security/gnupg20
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195678 Rene Ladan changed: What|Removed |Added CC||r...@freebsd.org Resolution|--- |Overcome By Events Status|New |Closed --- Comment #3 from Rene Ladan --- security/gnupg20 expired yesterday, closing this PR. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
Firefox 57 is eating my system
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? While I'm at it, what about OSS? Not nearly as critical, but would be nice. I'm not on gecko@, so please copy me. Thanks! -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
Re: Firefox 57 is eating my system
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. ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
