Date: Wed, 09 May 2018 06:36:07 +0000 From: bugzilla-noreply@freebsd.org To: gecko@FreeBSD.org Subject: [Bug 226476] www/firefox: update to 60.0 Message-ID: <bug-226476-21738-q7OzeBwzCv@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-226476-21738@https.bugs.freebsd.org/bugzilla/> References: <bug-226476-21738@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226476 Jan Beich <jbeich@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|In Progress |Closed --- Comment #50 from Jan Beich <jbeich@FreeBSD.org> --- rc2 became release: https://hg.mozilla.org/releases/mozilla-release/rev/3202d5534730 (In reply to jakub_lach from comment #46) Can you try removing files/patch-bug1438678 and files/patch-z-bug1436911 ? Those improve how child processes are initialized and, normally, should've been part of 61.0. Did you toggle any prefs in about:config? In particular, gfx.xrender.enabled=true or layers.acceleration.force-enabled=true may degrade stability. Can you check about:support what audio backend is used? There's no perfect one, each has issues. (In reply to Graham Perrin from comment #48) > Would you like this spun off to a separate bug report in > either the Mozilla or FreeBSD area? Try bug 227850 then check on Linux and macOS. FreeBSD uses posix_spawn (like macOS) to create child processes. It wouldn't hurt to file a bug on Mozilla tracker but "_momentary_ appearance of a content process" may be a normal behavior given Firefox keeps the number of content processes limited (unlike Chromium). -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-226476-21738-q7OzeBwzCv>