Other Chromium Legacy: Google Chrome for OS X 10.7 – 10.9

[Sh3ldon]

A question I frequently ask myself is this: "Since Tahoe will be the last operating system for Intel processors, once it reaches the end of its update cycle, and with it Safari, what will all Intel machine owners do to continue having an up-to-date browser if they want to stick with a Chromium-based browser?"
The problem doesn't seem to arise for those who want to use Firefox Dynasty (thanks to those who keep it updated), but is it possible that there isn't any capable developer willing to continue the Chromium Legacy project while for Firefox the problem doesn't seem to exist?

 

[f54da]

> Chromium-based browser

If you're ok with webkit based, there is Orion which I think has support down to 10.12 or so?

 

[Sh3ldon]

> Chromium-based browser

If you're ok with webkit based, there is Orion which I think has support down to 10.12 or so?

I tried Orion and I like the look and feel of Safari, but unfortunately many sites do not work properly. I tried with Chrome and they work. An open source clone of Chrome with the same compatibility of the one made by Google would be great and it would extend life of our unsupported mac.

 

[Sh3ldon]

@Wowfunhappy is there really no chance that this project will be revived and maintained?

 

[Wowfunhappy]

Guys, respectfully... it's nice to want things. 🙂

The fact we ever got a Chromium backport is a miracle. The fact we still have a Firefox backport (despite some issues with Github at the moment that I'm pretty sure will be resolved) is also a minor miracle. The complexity of modern web browsers is insane.

 

[Sh3ldon]

Mine was obviously a request and absolutely not a demand. I understand that it's difficult to bring browsers forward even for older operating systems, but it's the only way we have to avoid planned obsolescence. Thanks to the programmers who are able to breathe new life into our old hardware.

 

[wicknix]

but it's the only way we have to avoid planned obsolescence.

Not always ideal, but installing Windows or Linux in a virtual machine helps avoid this. Heck WinXP is lightweight and has Supermium. Installing XP or Win7 in a VM barely uses any resources and is a great way to have a current browser on older Macs when all else fails.

 

[Wowfunhappy]

I understand that it's difficult to bring browsers forward even for older operating systems, but it's the only way we have to avoid planned obsolescence.

So then use Firefox Dynasty. I respect that you might have a preference for Chrome, but beggars can't be choosers here.

 

[Sh3ldon]

So then use Firefox Dynasty. I respect that you might have a preference for Chrome, but beggars can't be choosers here.

You're absolutely right, and I can't thank enough the developers who freely offer their time and expertise to provide us with updated browsers for our older systems. My preference for Cromium over Geko is that almost all websites are optimized for Chrome. Chromium Legacy was the best!

 

[Sh3ldon]

@Wowfunhappy or for anyone who wants kindly to answer this question: I'm using Safari on a 2015 iMac with Sequoia patched with Open Core Legacy Patcher. It's more secure than Firefox ESR if i used it on Monterey (which is the last version officially supported by Apple for my iMac)? I know this is a discussion for Chromium Legacy and may be it would be better to open a new discussion for the same question.

 

[aurora72]

I'm using the Chromium-127.0.6494.0 on my Lion 10.7.5.
It's triggering random Kernel Panics causing me to hard shut down the computer.
Last KP report I got yesterday. What can be done to remedy the problem?
Note: I'm using the Firefox-68.12.0p2 on the same computer and it's running KP-free for years. So this is apperantly a Chrome/Chromium issue.

 

[Wowfunhappy]

I'm using the Chromium-127.0.6494.0 on my Lion 10.7.5.
It's triggering random Kernel Panics causing me to hard shut down the computer.
Last KP report I got yesterday. What can be done to remedy the problem?

You can fix the kernel panics caused by Chromium Legacy by installing the attached kext. Unfortunately, this is fundamentally a bug in the kernel (it's supposed to be impossible for standard "userspace" apps to cause kernel panics), so it has to be fixed in the kernel.

I included an installer script, but note that I just quickly copied the files out of my old Preference Pane, you may need to adjust the paths, I'm not sure.

You can read much more about this (almost certainly more than you'd like to know) here: https://github.com/blueboxd/chromium-legacy/issues/44

 

[f54da]

The above panic isn't from kqueue though, it's related to login items

Edit: wait nvmind it probably is the kqueue issue, the crash above wouldn't show the kernel side of things and is probably unrelated

 

[Wowfunhappy]

The above panic isn't from kqueue though, it's related to login items

Edit: wait nvmind it probably is the kqueue issue, the crash above wouldn't show the kernel side of things and is probably unrelated

Yeah I just kind of assumed OP attached the wrong crash log, since there's no way there's a different kernel panic that only occurs when Chromium Legacy is running and none of us have noticed before.