M109.0.5414.172 - Final M109 Release

[Alex313031]

[UPDATE]: It turns out they made 3 more minor versions, with the true final one being 109.0.5414.172. I also screwed up Widevine on the last .169 release. So I am rebuilding and uploading them here. I also never completed the release notes for the previous one, so see the bottom for changes between 159 - 172

• Chromium bump from 109.0.5414.159 > 109.0.5414.169 and now to > 109.0.5414.172
• This is the LAST version of M109. It includes fixed for two major security vulnerabilities in libwebp and libvpx. See the new security policy for info about submitting security bugs, and a list of fixed vulnerabilities (which will be updated henceforth). If you use any of my Electron apps, those were also recently fixed.
• Next version will be based on Supermium M118
• Backported these patches from latest Thorium (Includes history of 159 - 169 & 169-172):

• F

---

This discussion was created from the release M109.0.5414.172 - Final M109 Release.

[libreom]

Hi when will thorium-win7 based on supermium be released?

[Conflituoso]

Hi.

There won't be a WIN32 version of the 172?

[Conflituoso]

Thanks a lot for the WIN32 version!!!

[Ru-Sky-Gin]

Thanks bro for the support on Win7!
Finally found you!

[NAKADZI]

🤩Thank you very much for making SSE2 builds ✨
It saved my friend's 2005 netbook (and not only) ♥️

[Dratas]

Hello just mine 5cents,but when trying log-in to discord.com after i write user/pass combos,lastest build thorium SSE3 for win 7 M109.0.5414.172,shows for me STATUS_ACCESS_VIOLATION error,what to do?not tried normal release and SSE2.

[Kame03]

I have the same issue with Discord.

[Kame03]

I've opened a bug report: Alex313031/thorium#442

[Alex313031]

@Dratas @retapich @Ru-Sky-Gin @Kame03 This was fixed in the latest M122 release.

[Stepman123]

Version 122 is too heavy for older equipment, so it cannot replace 109.

[Kame03]

Great thanks for letting me know. ---- On Wed, 03 Apr 2024 08:35:49 +0200 Alex ***@***.***> wrote ---- @Dratas @retapich @Ru-Sky-Gin @Kame03 This was fixed in the latest M122 release. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>