Date: Tue, 10 Apr 2018 12:12:44 +0000 From: bugzilla-noreply@freebsd.org To: gecko@FreeBSD.org Subject: [Bug 226476] www/firefox: update to 60.0 Message-ID: <bug-226476-21738-NWxUWT2zWc@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 --- Comment #29 from D. Ebdrup <debdrup@gmail.com> --- (In reply to Jan Beich from comment #27) >OpenBSD But I'm using FreeBSD, so I don't see how that's relevant. Still, I've upped kern.ipc.shmall to 262k instead of the 131k it was at - so whatever limits there may be shouldn't be a problem. >Logging I'll try messing around with it anyhow - with pkg, it's remarkably easy to switch between the working and non-working version of Firefox, so I should be able to tell if it reports anything different, and possibly find out what that means. >Disable DTRACE option The thing is, I only get the dtrace errors if the DEBUG option is turned on. The first package that I built, and that I'm using to test with, is built with default options and didn't get any errors. Long of the short of it is - Don't feel you have to delay the port on my account, though - if I need webrtc, I'll install the working version temporarily, no reason to have that delay a new version of the port going out. If I find a real bug in FreeBSDs port, or better yet a fix, I'll file a separate report. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-226476-21738-NWxUWT2zWc>