I think the Firefox Dynasty guys have used the Mozilla developer channel that allows parallel installations. I don't know what your machine is like, but I recommend that when you unzip the download from Github you open Firefox from the same folder. Don't transfer 132 to programs. That will allow you to start Firefox 132 and test it without breaking 115.17. But the Mozilla cloud works very well and it configures itself in two minutes. It has one drawback and that is that when you close Firefox it will reset the configuration and when you come back you have to start again. For me it works for testing. If you transfer to programs you avoid that hassle but you can't undo it.
Got a tip for us?
Let us know
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
- Thread starter Wowfunhappy
- Start date
-
- Tags
- web browsers
- Sort by reaction score
They had a thread of complaints on Github from people who were unable to start on any version. They have deleted it. The last zip they posted allows me to run perfectly on Mojave and High Sierra but not on Capitan, Yosemite and Mavericks. In this same forum in the browser thread there is a post with a user who by applying a command has made it work on those lower versions.
Ah, I think we’re talking at cross purposes. When you previously said "In a separate installation I test Firefox 132 in High Sierra, which Mozilla has updated and will no longer need Github", I assumed that 'not needing Github' meant you were testing the latest Mozilla Firefox 132 not the Github Dynasty version.
So you're actually testing Firefox Dynasty 132 in High Sierra, not the Mozilla release?.
I'm happy to report that 132 works fine in my 10.13 VM including Widevine (which isn't broken there).
So here's my situation:
1. Everything I need runs fine in Mavericks where Chromium Legacy is my browser of choice for nearly everything.
2. For DRM streaming I can use Firefox Dynasty 132 in the 10.13 VM, so I don't need to worry about what will happen in March 2025.
Mozilla version 132 is not compatible with High Sierra. Mozilla ends its cycle with 115xx. So you have to use the "adapted" version from Github, obviously! 😅 The Mozilla DMG 132 you see in the screenshot will flag it as forbidden
Good luck !
Release 132.0 · i3roly/firefox-dynasty
i am jumping the gun assuming BUILD1 will be RELEASE, but oh well. now libsoundtouch is in libxul. sorry big g @glandium, doin' you dirty here
github.com
Crash log:
Release 132.0 · i3roly/firefox-dynasty
i am jumping the gun assuming BUILD1 will be RELEASE, but oh well. now libsoundtouch is in libxul. sorry big g @glandium, doin' you dirty here
Code:
AvailablePhysicalMemory: 95830016
AvailableSwapMemory: 824705024
BackgroundTaskMode: 0
BuildID: 20241025145248
CrashTime: 1730305710
DOMFissionEnabled: 0
DOMIPCEnabled: 0
HeadlessMode: 0
InstallTime: 1730257229
LastStartupWasCrash: 0
MacAvailableMemorySysctl: 1
MacMemoryPressure: Normal
MacMemoryPressureCriticalTime: Unset
MacMemoryPressureNormalTime: 1730305710
MacMemoryPressureSysctl: 1
MacMemoryPressureWarningTime: Unset
ProductID: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
ProductName: Firefox
PurgeablePhysicalMemory: 18034688
ReleaseChannel: default
SafeMode: 0
SecondsSinceLastCrash: 48457
StartupCacheValid: 0
StartupCrash: 1
StartupTime: 1730305710
SubmittedFrom: Client
Throttleable: 1
TotalPhysicalMemory: 4294967296
UptimeTS: 17.33206496
Vendor: Mozilla
Version: 132.0
This report also contains technical information about the state of the application when it crashed.I recommend you open a thread and ask them. I don't see anything in that report. I did have problems with the first zips and I still have them with the lower versions
https://github.com/i3roly/firefox-dynasty/issues
I love and use both Firefox-Dynasty & Chromium Legacy.
As for Chromium Legacy I'm now using version 120 (I was very happy with 124).
I tested some Firefox-Dynasty versions in different MacOS versions from 10.8 Mountain Lion to 10.14 Mojave, I'll share my results:
Firefox-Dynasty 128 versions works in MacOS from 10.8 to 10.14
Firefox-Dynasty 129.0.1 works in MacOS from 10.8 to 10.9 and 10.14
Firefox-Dynasty 130.0.1 works in MacOS from 10.8 to 10.9 and 10.14
Firefox-Dynasty 131.0.1 works in MacOS from 10.8 to 10.9 and 10.14
Firefox-Dynasty 132 works in MacOS from 10.8 to 10.9 and from 10.12 to 10.14
Firefox-Dynasty initially crashed because I used Firefox profile selector, I needed to turn it off "Set as default profile" with url about: profiles.
Edited to remove the emoticon from about: profiles
Just tested to be able to navigate various sites, didn't test DRM. Tested in actual MacOS versions not virtual.
As for Chromium Legacy I'm now using version 120 (I was very happy with 124).
I tested some Firefox-Dynasty versions in different MacOS versions from 10.8 Mountain Lion to 10.14 Mojave, I'll share my results:
Firefox-Dynasty 128 versions works in MacOS from 10.8 to 10.14
Firefox-Dynasty 129.0.1 works in MacOS from 10.8 to 10.9 and 10.14
Firefox-Dynasty 130.0.1 works in MacOS from 10.8 to 10.9 and 10.14
Firefox-Dynasty 131.0.1 works in MacOS from 10.8 to 10.9 and 10.14
Firefox-Dynasty 132 works in MacOS from 10.8 to 10.9 and from 10.12 to 10.14
Firefox-Dynasty initially crashed because I used Firefox profile selector, I needed to turn it off "Set as default profile" with url about: profiles.
Edited to remove the emoticon from about: profiles
Just tested to be able to navigate various sites, didn't test DRM. Tested in actual MacOS versions not virtual.
Last edited:
DRM won't work at all in Mavericks as Widevine is broken there. I've not tested in my 10.12 VM, but Dynasty plays DRM in 10.13 (e.g. Audible, Prime, ITVX). I've not tested Chromium there as it's not intended for post-Mavericks.
I think Chromium Legacy will work fine post-Mavericks, it's just my PrefPane that you shouldn't use.
I've copied it into my 10.13 VM, but it's so extremely slow (freeze slow...) I've given up on it. Having said that, it's not just Legacy - Chrome ESR is just as slow. I don't know if it's being in a VM that's caused it, or something else? Anyway, Firefox works just fine so I'm happy enough with that.
That's what I'm getting too - and a search for i3roly doesn't bring up any of his repositories. However, I believe the same thing happened to bluebox as well, but later his stuff was reinstated?.
To everyone having problems with Chromium Legacy. The culprit is google, they release 'something' right about the time we all started having problems.
I'll explain best to my ability.
I too began to have the instant-constant crashs. Found it strange that all of my Macs crashed, 10.8, 10.10, 10.13, and 10.14. began testing by renaming the Chromium profile folder, launched Chromium Legacy. Low and behold Chromium Legacy ran fine for 2 - 5 minutes. Repeated my actions several times and found that reusing the profile folder caused a near instant crash, starting with an empty folder, ran for a couple of minutes.
On a hunch, I removed Chromium Legacy's permissions in Little snitch, and launched Chromium Legacy from a blank profile folder. Chromium Legacy did not crash, loaded a random site and allowed Chromium Legacy's permissions in Little Snitch one at a time. In doing so i found that Chromium Legacy crashed when connecting to google. Started over with a blank profile folder and this time i denied permission to anything google. Chromium Legacy ran for several hours with no problems. In fact the extensions I use crashed on a regular basis, prior to blocking connections to google, no they rarely crash.
As a result I added these to my pihole, don't know if all should be blocked. Please test for yourselves.
update.googleapis.com
content-autofill.googleapis.com
accounts.google.com
optimizationguide-pa.googleapis.com
Back to my first statement, i don't know what this 'something' that is pulled from one or more of the sites listed above, but it is the cause of the crashes.
Initially I was surprised that google would undermine open-source, but in all actuality google has beet petty during most of their existence, no?
As a suggestion, maybe blueboxd should fork off Ungoogled Chromium?
Google released a Widevine update recently - Legacy shows the current version, but Wvine is broken in 10.9, so I can't play any DRM video. However Wvine still works in 10.13 (in my VM, where I use Firefox for DRM, haven't installed Legacy there).
You don't run 10.9? Seems ok here apart from the 'blank web page' which often happens and is cured either by reloading the page or relaunching Legacy altogether.
I don't run Snitch
.
I don't know what a pihole is (apart from my mouth 🤣). However I run both YouTube and Gmail via Legacy, so disconnecting from Google would cause me serious problems
.
I don't think that google would undermine open-source, I just don't think it figures in their development thinking. But yes, they would often seem to be 'petty'.
yeah, i keep getting the issue where the page is loading infinitely and is blank
i can fix it by reloading
the crashes have gotten better, but are still occasionally happening
...but that's what people have always been doing on this subforum. If you look at the front page of the Early Intel Mac forums, there's many active threads where people have been chronicling their hardware/software hacks and restoration projects involving older versions of OS X.
In fact, this very thread is a discussion about keeping old Intel Macs alive without Linux or OCLP through a backport of Chromium to 10.7+.