Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

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

Wowfunhappy said:
...oh. So then KQueueScanContinuePatch probably isn't the cause of the panic.
Click to expand...
I thought the panic was due to Chromium Legacy and the fixed kext included in the PrefPane was supposed to stop it. I might have gotten it wrong though. I indeed do have occasional panic here and there and thought it was Chromium Legacy that caused it. Wish I knew better.
 
The kext fixes a very specific panic that's triggered by Chromium Legacy. Look for a file with the extension ".panic" in /Library/Logs/DiagnosticReports. If it was the one caused by Chromium Legacy, this text will be near the top:

kqueue_scan_continue: - invalid wait_result
 
Wowfunhappy said:
Look for a file with the extension ".panic" in /Library/Logs/DiagnosticReports.
Click to expand...
Weird, there's none with .panic extension
Screen Shot 2022-07-16 at 10.08.14 PM.png
 
Wowfunhappy said:
It might not have been a kernel panic! A hard freeze is not necessary a panic. In fact, on Mavericks, a kernel panic triggers an automatic reboot.
Click to expand...
Yes, that's what happens (happened!) when I got kernel panics - there was always a panic report in Console after the reboot. A freeze is very rare, and usually resulted from a memory issue.
 
AlixSPQR said:
I tested the Canary build on El Capitan, and it worked fine. No official support yet, but maybe that will come?

github.com

GitHub - blueboxd/chromium-legacy: Latest Chromium (≒Chrome Canary/Stable) for Mac OS X 10.7+

Latest Chromium (≒Chrome Canary/Stable) for Mac OS X 10.7+ - blueboxd/chromium-legacy
github.com github.com
Click to expand...
I expect it will continue to work, Bluebox probably just hasn't updated the readme. I've used Chromium Legacy on High Sierra before (in order to test something) and even there, it worked fine.

Note that while I haven't tested it, I expect my PrefPane will not work properly on El Capitan, as it does some things (e.g. code injection) which usually make System Integrity Protection angry.
 
Last edited:
  • Like
Reactions: AlixSPQR
Many months ago I installed Chromium Legacy on El Capitan . Before official Chrome support ended. I knew that sooner or later I would and I anticipated it. The result is magnificent :apple: 👌
 
  • Like
Reactions: netsrot39 and AlixSPQR
Wowfunhappy said:
I expect it will continue to work, Bluebox probably just hasn't updated the readme. I've used Chromium Legacy on High Sierra before (in order to test something) and even there, it worked fine.

Note that while I haven't tested it, I expect my PrefPane will not work properly on El Capitan, as it does some things (e.g. code injection) which usually make System Integrity Protection angry.
Click to expand...
I tested your PrefPane and it worked fine, as far as I could see. I could install the stable build thanks to that*. Thank you for your work.

*Edit: Not necessary. I could install the stable version anyways, it just took some time to pass Gatekeeper (stating it's insecure, but then open it anyway with ctrl-click).
 
Last edited:
@Wowfunhappy >which usually make System Integrity Protection angry.
You can use ld_preload fine even with SIP enabled, so long as the executable doesn't have cs_restrict or hardened runtime. https://theevilbit.github.io/posts/dyld_insert_libraries_dylib_injection_in_macos_osx_deep_dive/ I suspect the 3rd party build of chromium doesn't have this set? (verify with codesign -dvvvvvvvvvvvv (not sure how many vs needed)).

And even if it does use hardened runtime, I've been able to just resign it myself to be able to dyld inject.
 
  • Like
Reactions: Wowfunhappy
When I dig into this Chromium Legacy version I noticed that it is managed, what does that mean in practice?

dump.png
 
Last edited:
AlixSPQR said:
When I dig into this Chromium Legacy version I noticed that it is managed, what does that mean in practice?

View attachment 2049614
Click to expand...
You're using my PrefPane, right? These are preferences it sets by default.

Some of these are my personal preference (I made the PrefPane for myself first and foremost). For example, I dislike how by default, if you're using Chromium and you sign into e.g. your gmail account, you automatically get signed into your Google account in the browser too. You can still enable this in the UI if you want (and in fact, you must enable it in order to e.g. sync bookmarks to your Google account), but the PrefPane turns it off by default.

Other settings are workarounds, or partial workarounds, for Chromium Legacy limitations. For example, some UI elements in Chromium Legacy lack a drop shadow, and so can be hard to see against a white background. One of those UI elements is the print preview dialog. To have one less UI element with this problem, I switch the print preview window to the native Apple print dialog instead of Chromium's custom one.
 
Last edited:
  • Like
Reactions: AlixSPQR
Wowfunhappy said:
You're using my PrefPane, right? These are preferences it sets by default.

Some of these are my personal preference (I made the PrefPane for myself first and foremost). For example, I dislike how by default, if you're using Chromium and you sign into e.g. your gmail account, you automatically get signed into your Google account in your browser too. You can still enable this in the UI (and need to if you want to e.g. sync bookmarks), but the PrefPane sets it off by default.

Other settings are workarounds, or partial workarounds, for Chromium Legacy limitations. For example, some UI elements in Chromium Legacy lack a drop shadow, and so can be hard to see against a white background. One of those UI elements is the print preview dialog. To have one less UI element with this problem, I switch the print preview window to the native Apple print dialog instead of the built in Chromium one.
Click to expand...
Thank you for your explanation! :)

Edit: I experience no UI problems in El Capitan without your PrefPane.
 
Last edited:
I'd hate to tell it yet before trying to have the RAM modules swapped I thoroughly cleaned the system from Chromium. Not a single system freeze since that. I googled for "chrome mac os freeze" and the search returned that quite a few people are experiencing the same issue.

They'd rather have made legacy Firefox (wishful thinking)

Please do not take it on your account, I really appreciate what you're doing. It's just the app itself that causes problems.
 
Modern operating systems are built to make it impossible for a userspace app like Chromium to freeze the entire system, unless there's some other problem.

Chromium is a complex app, so if you have an underlying hardware issue (e.g. bad memory), it's entirely plausible that Chromium could trigger the problem where most software usually does not. However, keep in mind that other software may still eventually trigger the problem, possibly with worse results such as data corruption.
 
Last edited:
After updating from version 105 to 106 on 10.9.5, all of the GPU acceleration is allegedly broken due to the GPU thread crashing. That said, there is still a GPU process running according to Activity Monitor. I know compositing was intentionally blocked for compatibility, but assuming that the "Graphics Feature Status" page wasn't lying to me previously and isn't now, does anyone know if this is now "expected" behavior on 10.9.5? I'm very grateful this project even exists, so I'm not exactly expecting a fix, but I'm just wondering whether or not this is intentional.
 
I still need to take a look myself, but the way to test this would be to try running something that uses webgl. E.g. https://webglsamples.org/aquarium/aquarium.html

That used to work on Chromium Legacy, albeit not necessarily with great performance, because everything is calculated by the cpu instead of the gpu. If it outright doesn't work now, that's a regression which bluebox will probably need to fix.

Edit: And yes, can confirm it broke in 106.
 
Wowfunhappy said:
I still need to take a look myself, but the way to test this would be to try running something that uses webgl. E.g. https://webglsamples.org/aquarium/aquarium.html

That used to work on Chromium Legacy, albeit not necessarily with great performance, because everything is calculated by the cpu instead of the gpu. If it outright doesn't work now, that's a regression which bluebox will probably need to fix.

Edit: And yes, can confirm it broke in 106.
Click to expand...
Got it, I guess I'll stick with 105 for now, then. Thank you for the reply.
 
There are two projects. There's Chromium Legacy itself, by Bluebox, which can be used by itself, and there's my PrefPane (the "downloader"), which adds an autoupdater and some other stuff.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back