chromium-62.0.3202.89

[bdubbs@…]

New major version.

[Pierre Labastie]

See ​https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop.html Excerpt:

 This update includes 35 security fixes.

[Douglas R. Reno]

Based off the security fixes, upgrading priority to "HIGHEST".

[Cheyenne McNutt]

DJ gave me permission around 3:30PM today to accept this and node.js as a test. I figure that it's a worthy first two packages, and I'll have Douglas help me with this, while he's working on his tickets (I'm getting on him about that).

[Douglas R. Reno]

As an update, Chey and I are working on this and node.js as I type this. The real killer here will be build time, but DJ gave us both notes on what to expect in this version.

In addition, there was one new CVE added in .75 - a stack overflow in the V8 component.

[Douglas R. Reno]

- CVE-2017-15398 (arbitrary code execution)

A stack-based buffer overflow has been found in the QUIC component of
the Chromium browser before 62.0.3202.89.

- CVE-2017-15399 (arbitrary code execution)

A use-after-free has been found in the V8 component of the Chromium
browser before 62.0.3202.89.

[Douglas R. Reno]

More security fixes!

[Douglas R. Reno]

We are still doing this jointly, but I'm pushing it under my account.

[Douglas R. Reno]

I can't get it to build at -j4 with 8GB of RAM without OOMing. My system has been hardlocked four times by this build, to the point where it ICEs every time.

I'm reassigning it to DJ on Cheyenne and I's behalf.

If I try this again at anything more than -j1, heed my notice: You need more RAM.

[bdubbs@…]

Although it slows things down a lot, make sure you have a large swap file until you get more ram. That will work around the OOM condition.

[bdubbs@…]

Fixed at revision 19495.