Date: Sun, 19 Jan 2014 14:01:05 +0100 From: Carlos Jacobo Puga Medina <cjpugmed@gmail.com> To: freebsd-chromium@freebsd.org Subject: Re: 32.0.1700.77 released Message-ID: <CAHHLbRO-KshnD76aMTCw9LF5GzHfVKZCuHDpkzb6zGKMCqOjVg@mail.gmail.com> In-Reply-To: <CAHHLbRPHazs%2BeSmoB6aoogB2mh7qKTnpg6HHaadustd62HsyoA@mail.gmail.com> References: <CAHHLbROUr2Pm%2BO%2BMeAbGS0WUJQoxU=41YM-J%2B7U35eQA0kme7A@mail.gmail.com> <CAHHLbRNCjxsrCwZS89NvAjVOW26WFO_y1L%2BqzsnnRAYThiFVqg@mail.gmail.com> <52D857FC.8090801@freebsd.org> <CAHHLbRNxfF7QB0p_dG3NmwvYXM33T5MbJN9NKNMg8HJ5tPU2Qw@mail.gmail.com> <CAHHLbRPHazs%2BeSmoB6aoogB2mh7qKTnpg6HHaadustd62HsyoA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ok. To be completely sure, I upgraded to 32.0.1700.95. No changes, Chrome still crashing as before. I got a full backtrace from the coredump: http://pastebin.com/GP9fUEBQ 2014/1/17 Carlos Jacobo Puga Medina <cjpugmed@gmail.com> > The current version is pending to be fixed, so I downgraded to previous > Chrome version which works fine. > > # rm -rf /usr/ports/www/chromium > # svn export -r 339634 svn:// > svn0.us-east.freebsd.org/ports/head/www/chromium /usr/ports/www/chromium/ > > --CJPM > > > > 2014/1/17 Carlos Jacobo Puga Medina <cjpugmed@gmail.com> > >> I've the same problem. The problem I encountered in chrome-32.0.1700.72 >> hasn't been corrected in the latest release. It failed at the same point= . >> Just checking the chrome commands (see all available in >> 'chrome://chrome-urls/') or trying to change the chrome configuration it >> hangs, throws a chrome.core and crashes immediately. >> >> I compiled the port using both GCC 4.8.3 and Clang 3.3 >> >> The FreeBSD Release that I'm using: >> % uname -a >> FreeBSD freebsd 9.2-RELEASE-p3 FreeBSD 9.2-RELEASE-p3 #5: Tue Jan 14 >> 23:02:12 CET 2014 charly@freebsd:/usr/obj/usr/src/sys/GENERIC i386 >> >> Regards, >> >> --CJPM >> >> >> 2014/1/16 Ren=E9 Ladan <rene@freebsd.org> >> >>> On 01/16/2014 15:45, Carlos Jacobo Puga Medina wrote: >>> > I installed it by passing the DDISABLE_VULNERABILITIES option, but I >>> > can confirm that the new chrome released doesn't work as expected. It >>> > crashes over and over again e.g. when I check the chrome >>> > version/plugins/chrome info (just typing 'chrome://command' in the >>> > address bar). >>> > >>> > I deleted the $HOME/.config/chromium directory, but no change in >>> > behaviour. So I will return to previous version. >>> > >>> Can you try updating to 32.0.1700.77 instead? .72 is a beta version but >>> has most likely less vulnerabilities than 31.0.* (which is now >>> unsupported). >>> >>> Ren=E9 >>> > 2014/1/16 Carlos Jacobo Puga Medina <cjpugmed@gmail.com >>> > <mailto:cjpugmed@gmail.com>> >>> > >>> > When upgrading chromium port shows that it has multiple >>> > vulnerabilities. >>> > >>> > =3D=3D=3D> chromium-32.0.1700.72 has known vulnerabilities: >>> > Affected package: chromium-32.0.1700.72 >>> > Type of problem: chromium -- multiple vulnerabilities. >>> > Reference: >>> > >>> http://portaudit.FreeBSD.org/5acf4638-7e2c-11e3-9fba-00262d5ed8ee.html >>> > =3D> Please update your ports tree and try again. >>> > *** [check-vulnerable] Error code 1 >>> > >>> > Stop in /usr/ports/www/chromium. >>> > *** [build] Error code 1 >>> > >>> > Stop in /usr/ports/www/chromium. >>> > >>> > =3D=3D=3D>>> make failed for www/chromium >>> > =3D=3D=3D>>> Aborting update >>> > >>> > >>> > >>> > >>> >>> >> >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHHLbRO-KshnD76aMTCw9LF5GzHfVKZCuHDpkzb6zGKMCqOjVg>