Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
New release is now available for OS X and PowerPC Linux.
Change log: https://github.com/wicknix/Arctic-Fox/compare/v27.12.0...v39.0

Cheers
Sad to say, same repeated crashes as earlier. Even after being offered to "refresh" it and keep some of the stuff (w/out addons), it keeps on crashing and I end up with a virgin installation. Wish I had time & energy to begin from scratch!
 
As also happened with the last update, after three forced reopenings, the dialog box appeared allowing Arctic Fox to be refreshed or started in safe mode. However, the safe mode option does not seem to work, as Arctic Fox then keeps crashing at startup. Thus, the only possible option remains to refresh Arctic Fox. Once the refresh is done, however, Arctic Fox 39.0 will start and work fine, even though Arctic Fox will then be in a virgin state again. I don't mind then, however, because I'm using Arctic Fox with the default settings anyway. And of course, we also have SpiderWeb and InterWeb for other use cases. :)

What I have noticed is the following. It seems that in Arctic Fox 39.0 you can't install extensions from the Pale Moon website anymore. Since I always had only two extensions in use, and those are Decentraleyes and uBlock Origin (Legacy), I can't tell if that applies to all extensions, but Decentraleyes, for example, can no longer be installed. A nice touch, however, is that as far as uBlock Origin (Legacy) is concerned, with firefox-legacy-1.16.4.30 you can now use the most current version without modifications, where up until Arctic Fox 27.12.0 you could only install version firefox-legacy-1.16.4.21 and older.
 
Piscatorius, what is better in this new version compared to 27.11? Is it worth it? Do some website work better with it for example? I hate to do that refreshing thing if not necessary. Thanks.
 
As also happened with the last update, after three forced reopenings, the dialog box appeared allowing Arctic Fox to be refreshed or started in safe mode. However, the safe mode option does not seem to work, as Arctic Fox then keeps crashing at startup. Thus, the only possible option remains to refresh Arctic Fox. Once the refresh is done, however, Arctic Fox 39.0 will start and work fine, even though Arctic Fox will then be in a virgin state again. I don't mind then, however, because I'm using Arctic Fox with the default settings anyway. And of course, we also have SpiderWeb and InterWeb for other use cases. :)

What I have noticed is the following. It seems that in Arctic Fox 39.0 you can't install extensions from the Pale Moon website anymore. Since I always had only two extensions in use, and those are Decentraleyes and uBlock Origin (Legacy), I can't tell if that applies to all extensions, but Decentraleyes, for example, can no longer be installed. A nice touch, however, is that as far as uBlock Origin (Legacy) is concerned, with firefox-legacy-1.16.4.30 you can now use the most current version without modifications, where up until Arctic Fox 27.12.0 you could only install version firefox-legacy-1.16.4.21 and older.

You may have a bad profile. I'd suggest running it from command-line mode to bring up the Profile Menu and then creating a new profile and running with that. You will have to add back your bookmarks, saved passwords, etc.

I've seen Firefox crash from things like cache fragments in the past.
 
Piscatorius, what is better in this new version compared to 27.11? Is it worth it? Do some website work better with it for example? I hate to do that refreshing thing if not necessary. Thanks.

Unfortunately, I cannot (yet) answer this question satisfactorily. I have only been able to test Arctic Fox 39.0 briefly so far. Therefore, I do not want to allow myself a final judgment. However, since Arctic Fox 39.0 brings a lot of bug fixes and certainly security updates, I think that installing the current version is worthwhile for that reason alone.

Whether Arctic Fox 39.0 renders one or another website better than an older version certainly depends on the website in question. As I said in an older post, my requirements for Arctic Fox are quite modest. Therefore I would like to pass this question on to other users.

First, I would like to test how well firefox-legacy-1.16.4.30 works with the current version of Arctic Fox. If this version of uBlock Origin works less well than I would like, then I will revert back to uBlock0-libre-1.16.4.8, the version I also use in SpiderWeb and InterWeb.
 
  • Like
Reactions: Johnny1068
You may have a bad profile. I'd suggest running it from command-line mode to bring up the Profile Menu and then creating a new profile and running with that. You will have to add back your bookmarks, saved passwords, etc.

I've seen Firefox crash from things like cache fragments in the past.

Do you really think it could be due to a bad profile? Well, that would mean that all Snow Leopard users who experience the problem have a bad profile. I can't imagine that this is actually the cause.

Also, with the exception of installing the two extensions I mentioned, I have always used Arctic Fox in the state in which it is shipped. That means no history, no bookmarks, no saved passwords, etc. When updating from version 27.11.0 to version 27.12.0, Arctic Fox also needed to be refreshed, and as far as I know a refresh creates a new profile folder and saves important data from the old Arctic Fox profile on the desktop in a folder named "Old Arctic Fox Data". However, since I deleted this profile folder and didn't copy anything from it to the newly created profile folder, the new profile can't actually have been corrupted by bad data either. Therefore I rather think that the cause of the error is buried somewhere deep in Snow Leopard.
 
Do you really think it could be due to a bad profile? Well, that would mean that all Snow Leopard users who experience the problem have a bad profile. I can't imagine that this is actually the cause.

Also, with the exception of installing the two extensions I mentioned, I have always used Arctic Fox in the state in which it is shipped. That means no history, no bookmarks, no saved passwords, etc. When updating from version 27.11.0 to version 27.12.0, Arctic Fox also needed to be refreshed, and as far as I know a refresh creates a new profile folder and saves important data from the old Arctic Fox profile on the desktop in a folder named "Old Arctic Fox Data". However, since I deleted this profile folder and didn't copy anything from it to the newly created profile folder, the new profile can't actually have been corrupted by bad data either. Therefore I rather think that the cause of the error is buried somewhere deep in Snow Leopard.

If you already created a new profile, then this wouldn't be the problem. Cached webpages and files are stored in the new profile.
 
  • Like
Reactions: Piscatorius
Do you really think it could be due to a bad profile? Well, that would mean that all Snow Leopard users who experience the problem have a bad profile. I can't imagine that this is actually the cause.
Indeed. Although I remember that when I started using AF (and registered on this forum) there were a few difficulties getting it to digest my Firefox profile, primarily its ≈1000 bookmarks (should still be there at posts xx on page yy of this thread). Things did work out in the end, and AF is still my primary browsing tool, with ± 53 addons. But there were a couple of quirks left, most noticeably the absent title bar, which I have to activate manually each time I launch it anew.
 
  • Wow
Reactions: Piscatorius
you can't install extensions from the Pale Moon website anymore.
Correct. Unfortunately they have decided to block downloads of their extensions unless you are using the "official" pale moon or basilisk browser. Without it you just get a "only on palemoon" button displayed. About all that's left is the classic addons archive ( https://github.com/JustOff/ca-archive ) and a few github repos that still host xul extensions.

Cheers
 
  • Sad
Reactions: Piscatorius
Unfortunately they have decided to block downloads of their extensions unless you are using the "official" pale moon or basilisk browser. Without it you just get a "only on palemoon" button displayed.

Well, that's too bad. But if the Pale Moon developers are happy with their decision, then let them have their fun. Fortunately, for me personally, it doesn't make much of a difference, since uBlock Origin (Legacy), the most important extension of all in my opinion, is still available. The loss of Decentraleyes for Arctic Fox is something I can get over quite well. It is much worse for all the users who use many more extensions than I do.
 
Correct. Unfortunately they have decided to block downloads of their extensions unless you are using the "official" pale moon or basilisk browser. Without it you just get a "only on palemoon" button displayed. About all that's left is the classic addons archive ( https://github.com/JustOff/ca-archive ) and a few github repos that still host xul extensions.
Actually, it's the Pale Moon users that may end up being the losers. I use PM in Linux for a couple of Snow Leopard-refractory sites, and with an update some months ago they've also managed to cut off their users from using a bunch of addons, including Form History Control.

Else, I just had a look at my PM/Linux installation. Seems like all the xtensions are there, ready to be dug out of the profile. Wouldn'it then just be a question of modifying them and import them (as we once did to import them in SpiderWeb)? Anybody needs one in particular, just ask, I'll do my best (assuming that's forum-legit.)
 
Last edited:
  • Like
Reactions: wicknix
I tried to fake it with interweb and spiderweb as those are based on a similar codebase as pm28 and it didnt work. However the UA override works on the winxp forks of pm29. Guess we could try it on AF at some point and see what happens.
 
  • Like
Reactions: Piscatorius
Today on Bing

Arctic fox - Microsoft Bing.jpg


Arctic fox, Dovrefjell-Sunndalsfjella National Park, Norway
©️ Andy Trowbridge/Minden Pictures
 
Question for wicknix:

I've been able to get version 39 running on most of my Intel Macs with Snow Leopard by deleting/renaming the ArcticFox folder in both ~/Library/Application Support/ and ~/Library/Caches/...

But I have two that crash with an "illegal instruction" error and a friend's computer does the same. Strangely enough all three machines have the Core 2 Duo P8400 cpu.

Are there any other places Arctic Fox writes files/parameters to? If so, should I delete/rename what's there?

These installs might've run a 64-bit version in the past too... ArticFox builds are now 32-bit only or...?

Thanks for any info!
 
Not only this Core 2 Duo/3.06GHz but also this Core i7/2.3GHz.

I had suggested earlier that the issue might be related to the original installation in what they called "International English" (or possibly any installation in another language than US English?) But now, upon checking the relevant hardware specs on Apple’s site (here and here), I can see that the configurations of both machines were “optionals" (and as such not obvious at all on Apple's pages).
 
Interesting about the p8400 cpu. I think you have all directories covered. Sadly this issue is still 10.6 specific and pinpointing the commit/bug fix that broke it has not been easy. For now i'd suggest InterWeb on those machines.

The original builds were 64bit back in 2018/2019 until i figured out how to build 32bit for better compatibility with plugins and core solo machines.

Cheers
 
  • Like
Reactions: netsrot39
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.