Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 24 Jul 2015 18:08:21 +0000
From:      bugzilla-noreply@freebsd.org
To:        chromium@FreeBSD.org
Subject:   [Bug 201543] www/chromium: chrome processes stuck at 100% cpu
Message-ID:  <bug-201543-28929-6k7dUkop9I@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-201543-28929@https.bugs.freebsd.org/bugzilla/>
References:  <bug-201543-28929@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=201543

Tony Narlock <tony@git-pull.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tony@git-pull.com

--- Comment #12 from Tony Narlock <tony@git-pull.com> ---
(In reply to pete from comment #11)

(this should probably be in 196770, but I don't think Pete is CC'd on it.)

Hi Pete, I am in another ticket
(https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196770) and I saw you were
producing working chromium builds with DEBUG symbols,

I'm wondering, what environment / build settings (freebsd version,
/etc/make.conf, etc) do you use to get builds with debug symbols working
correctly?

-- 
You are receiving this mail because:
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-201543-28929-6k7dUkop9I>