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

I use ArcticFox Version: 27.9.15 (32-bit) every day as main browser, no bug, no crash (quit) from the beginning.

I meet some behaviour I would report if it can help.

Sometimes when I launch ArcticFox, the window is full screen, not really annoying.

Main problem, the behaviour with the steetview of Google Maps. I get the view but it becomes hard to move left or right side with the mouse. Even to go forward seems to be very long, when it succeed...

For information, I get the same with NewMoon 27.9.4, Firefox 45.9 ESR is OK.

On some web pages such as the portal of my provider, certain scripts seem to run causing the colored wheel several seconds I just have to wait without any error message. With Safari 5.1.10 I've an option to stop that on developpement menu (Desactive Runaway JavaScript Timer), can I manage that with ArcticFox ?

Thanks for your support ;)
 
Last edited:
On some web pages such the portal of my provider, certain scripts seem to run causing the colored wheel several seconds I just have to wait without any error message. With Safari 5.1.10 I've an option to stop this on developpement menu (Desactive Runaway JavaScript Timer), can I manage that with ArcticFox ?
I get that on a few sites too. Often the little progress bar I've installed in the Tab shows that the page never finishes loading. In a way things were easier in Firefox, with NoScript.

The quick, immediate workaround is to press old +.

Else you can install an addon like ScriptBlock 1.0.0 or YesScript 2.2. Both of them remember your choice. If you need to activate a site's scripts again (some even use scripts to activate in-page links), just click on the addon's icon to toggle script activation, then reload the page.
 
The quick, immediate workaround is to press old +.

Don't run, the script keep on so the colored wheel. I tried . no more result...

Else you can install an addon like ScriptBlock 1.0.0 or YesScript 2.2. Both of them remember your choice. If you need to activate a site's scripts again (some even use scripts to activate in-page links), just click on the addon's icon to toggle script activation, then reload the page.

I prefer to not disturb all the sites where the scripts run by blocking their display just for one site, my provider portal for now.

Thanks for your suggestion.
 
Don't run, the script keep on so the colored wheel. I tried . no more result...

I prefer to not disturb all the sites where the scripts run by blocking their display just for one site, my provider portal for now.
As far as I have experienced, these addons only block the scripts of the site you're on.

However, other things can interfere too. Funny you should ask today: a little while ago, I had to do some transactions on a banking site I hadn't accessed since moving to ArcticFox. At the beginning I couldn't even get the most elementary functions to show up. Thus,

- 1. Allowed all of that bank's cookies permanently
- 2. Disabled AdBlock Latitude on their site
- 3. Disabled uBlock Origin, again only on that site

As I did these things, reloading the page after each one of them, the site was gradually getting functional again. Yet, I couldn't get it to show the new transaction page.

So I quit AF,

- 4. changed the server to a server in the bank's home country,

relaunched AF. Upon which everything worked like a charm, as it used to in Firefox.

Hard to tell which of these steps resolved the issue (was in a hurry to get it over with), or possibly only relaunching after any one of them. Maybe all this is not related to your specific issue, but it just tells us that there's a lot of things that can interact with each other. Oh yes, I was forgetting that earlier in the day I'd changed the User Agent from Firefox 5x something to IE 10, so who knows…
 
First, I try to use ArcticFox itself, so I'm searching a way through about:config options. I'm not a geek, the filter "script" helps ;)

The add-on Config Comments helps too.

What I found :
Code:
dom.global_stop_unresponsive_script;true
with comment Stop all scripts in a compartment when the "Stop script" button on the "Unresponsive script" dialog is used.
But no "Stop script" button on my bar and no dialog.

Others lines I don't understand and don't touch :

browser.urlbar.filter.javascript;true

dom.max_script_run_time;20

Any idea ?
 
Wow, a PowerPC Forum. I have a PowerMac g5 at home which is being used as furniture at the moment. I used to build optimized Firefox builds back in 2007 and 2008 and they are still there at http://www.vector64.com/elliott.html

Are these new builds based on later versions of Firefox? I should set up the old system and take a look. I'd have to reconfigure a new KVM though.
 
  • Like
Reactions: wicknix
... Are these new builds based on later versions of Firefox? I should set up the old system and take a look. I'd have to reconfigure a new KVM though.

Hi, indeed they are. Wicknix took the Palemoon browser (27.9.4) code that is more or less in sync with Firefox 50 and up (2016 to 2018) and managed to get it compiled and running for Snow Leopard (OS X 10.6). That was great. As Palemoon 28.x too much depends on the new APIs of OS X 10.7 and up, now we got this separate Arctic Fox fork, and that's great, too! Mr. Wicknix did outstanding work, as now the PowerPC users have (at least with Linux) a chance to use modern https:// pages. Let's see if the OS X 10.5 users will soon be happy, too.
 
@madbiker31 : Your best option as mentioned above is to install a script block add-on. They will give you a button by the url bar. Simply click it for javascript on/off. They will toggle only for sites you blacklist, and wont mess with sites that aren't. You could also try setting dom.max_script_run_time;20 to a lower number (try 10). However that might break heavy JS sites like facebook.

Cheers
 
  • Like
Reactions: netsrot39
@wicknix The scriptblock add-on, for example, can kill javascript on a site, but I'm afraid that the web page will not display correctly because it contains other necessary scripts. Not only the crazy one, or I missed something ?

I'm going to try different numbers to see.

Thanks for the ideas.
 
@wicknix The scriptblock add-on, for example, can kill javascript on a site, but I'm afraid that the web page will not display correctly because it contains other necessary scripts. Not only the crazy one, or I missed something ?
I think you're right. I access this news site practically every day. Pages never load completely in AF, and while they keep on churning AF gets noticeably slower. So having Scriptblock activated all the time for this site saves me the trouble of pressing +. for each page. But if for example I want to post a comment, I have to toggle Scriptblock and refresh the page. After posting the comment I toggle ScriptBlock once again. Sounds clumsy, but NoScript was far from being perfect either — can't count the sites that weren't quite functional because googletagmanager or some other apparently irrelevant google script was forbidden.
 
@wicknix I tried, I report :)

A script blocker is too much, the web page don't load completely, normal, so I removed.

Setting 20 to 10 was worse but for the first time I had the unresponsive script dialog :D Why not before ? So back to 20. Now I've the name of the bad guy.

@RobJos I access everyday the same news site ;) in french version, I get some slow when there is a video running in the pictures displayed at the begining.
 
(…) , the web page don't load completely (…) Now I've the name of the bad guy.
Funny, there was a time, long ago, when I used to get that a lot with Firefox. The worse thing was that it often wouldn't stop, regardless of the option I selected, and I ended up having to force quit FX. But that syndrom went away, not sure why, maybe with a later version. On AT, so far, it has happened once only. And the naughty script stopped as soon as I told it to.

@RobJos I access everyday the same news site ;) in french version, I get some slow when there is a video running in the pictures displayed at the begining.
Strange, I never get such videos at the top. Maybe there are some further down on the pages, and maybe it depends on the national/regional version of the portal.

If that bothers you, you could try using the addons Autoplay Toggle (Non-Restartless) 1.0.1 (always have it set to not play) and Expose Noisy Tabs 1.1.1 (set to "Prevent automatic media playback for background tabs"). Can't live without them if, say, I'm listening to iTunes with the headphones on while opening some YouTube tabs in AT.

Quite useful also in relation to whether scripts are blocked or not, the progress bar in the Tab, which I think (not sure) comes with the addon Tab Mix Plus 0.5.6.0. As on the above-mentioned news site:

Scripts not blocked:
ScriptsNotBlocked.jpg


Scripts blocked:
ScriptsBlocked.jpg


Enjoy...
 
I've installed AF 27.9.15 (32bit variant) on ubuntu mate 16.04 lts for ppc64 on a G5. Runs like a charm... no crashes, however I have a bookmark menu but none of my bookmarks. I have a toolbar menu with only one (1) entry... about:config. When I open the sidebar everything is there... all my bookmarks were restored from a .json file created on FF 47 on the same G5. Any thoughts?
 
Hmm. I'd delete that profile, restart AF for to create a clean profile, then export your bookmarks from FF47 to a html file, then import the bookmarks.html to AF. See if that fixes it. AF (and PM) differ from FF enough that copying bits of a FF profile can sometimes have adverse effects.

Cheers
 
I just tried ArcticFox Version: 27.9.16 64-bit, it crashs at startup everytime, all add-ons disabled or not.

If a crash log can help.
 
It's our favorite error, responsible for another crash. At it again, it seems.

<jemalloc>Compile-time page size does not divide the runtime one.
Segmentation fault
 
Last edited:
@madbiker31 @RobJos : Working fine on 10.6 and 10.8 here. Anyway, i rebuilt and uploaded again. Give it a whirl and let me know if it works. Might have just been a bad upload/download. Thanks.

@z970mp : Those contributed builds disable jemalloc and/or altivec in their builds to work on those amiga machines and/or other linux releases. My builds are made for debian 9 / ubuntu 16.

Cheers
 
  • Like
Reactions: z970
Hmm. I'd delete that profile, restart AF for to create a clean profile, then export your bookmarks from FF47 to a html file, then import the bookmarks.html to AF. See if that fixes it. AF (and PM) differ from FF enough that copying bits of a FF profile can sometimes have adverse effects.

Cheers
Deleted .mozilla, restarted AF, opened newly created .mozilla which contained one (1) empty folder... Extentions. Any thoughts?
 
@madbiker31 @RobJos : Working fine on 10.6 and 10.8 here. Anyway, i rebuilt and uploaded again. Give it a whirl and let me know if it works. Might have just been a bad upload/download. Thanks.
Good, launches fine this time. I'll let you know if there are any quirks. Took a look at the changelog, got accused of having a glazed look. Is there another file that tells us common humans about new features, bug fixes etc.?
 
Deleted .mozilla
Sorry, i could have been more clear where AF's profile is. In Linux AF's profile resides in ~/.org.wicknix/arctic fox/, not ~/.mozilla

@RobJos : The changlog for this release is nothing but mozilla based bug fixes and a few security updates. It's not supposed to make sense. Just know that they are good things. Like healthy treats for your browser. ;)

Cheers
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.