Pale Moon forum

Hello, I've just updated to 27.0.1, but I am going to revert back to the previous version. The newer version requires an upgrade to AB Latitude and once that is installed, the browser takes a very long time to open up. When I disable ABL, things are back to normal and everything is fine.

Part of the problem may be at this end - I'm running an old ThinkPad T60p with an early dual core processor. Perhaps those with faster computers are having better luck.

Roger Fink wrote:Hello, I've just updated to 27.0.1, but I am going to revert back to the previous version. The newer version requires an upgrade to AB Latitude and once that is installed, the browser takes a very long time to open up. When I disable ABL, things are back to normal and everything is fine.

Part of the problem may be at this end - I'm running an old ThinkPad T60p with an early dual core processor. Perhaps those with faster computers are having better luck.

Hello!

I think that maybe the new ABL needs a clean install, please clean your cache/history/cookies and update the lists of ABL. I hope this can speed up the process of starting Pale Moon!

Lyceus

I know I'm not explaining this quite right, but that's the way 3.5 works. Something to do with loading all the filters before the browser loads. I'm sure Tobin can explain it better than me. (This lag is really pronounced with older computers; I know from experience.)

EDIT:
MC explains it in passing here: https://forum.palemoon.org/viewtopic.php?f=46&t=10414&p=72210#p72205

Thanks for the three replies to my post, including especially the one that was lost when I deleted my initial follow-up post, which was not a good move.

But to the matter at hand - even acknowledging that my old hardware has something to do with the delay, I still think having the ABL delay occur after the launch is the better solution. If the design of the browser and add-ons were a unified effort from a single source (which I realize is impossible), the browser launch delay would never have been seriously considered IMO. The way it is now suggests that the browser is subordinate to the extension. It also undermines the tradition of extensive backward compatibility which I think is a great feature of this browser. I'm glad the developer feels he has solved his problem, but he's done it at my expense.

I hope there is an upgrade to ABL that fixes this. In the meantime I'm back to 26.5.0, since at the moment it is providing a much better overall browsing-with-ABL experience.

Slightly off topic, but the only reason I was able to revert successfully was because I had saved an older version of ABL (as I recall Win-7 System Restore kept the ABL upgrade). Since this kind of situation arises from time to time, I'd like to suggest keeping the next-to-last version of all extensions available for download.

lobocursor wrote:

Roger Fink wrote:Hello, I've just updated to 27.0.1, but I am going to revert back to the previous version. The newer version requires an upgrade to AB Latitude and once that is installed, the browser takes a very long time to open up. When I disable ABL, things are back to normal and everything is fine.

Part of the problem may be at this end - I'm running an old ThinkPad T60p with an early dual core processor. Perhaps those with faster computers are having better luck.

Hello!

I think that maybe the new ABL needs a clean install, please clean your cache/history/cookies and update the lists of ABL. I hope this can speed up the process of starting Pale Moon!

Lyceus

Hi,

Thanks for this, unfortunately it didn't solve the problem for me. Since installing version 27 (27.01 now) Pale Moon is slow (I mean sloooow ) at start up. Since there's no splash screen, one has no idea if Pale Moon is really starting or not. Compared to version 26 it takes about three times longer to load. Although a bit annoying, I can live with it. If this is a common experience, others (new users) might not be so understanding.

For the record, both on my Windows 7 and Kubuntu machine the behavior is the same.

Edit: Timed startup, from clicking the icon to interface show: 16 seconds.

HTH
Jottum

Roger Fink wrote:the browser takes a very long time to open up.

+1
with abl 3.0.3.1 2sec to browser start + 1 sec to unfreeze )) feels all loads sync
with abl 3.5 waiting....nothing happened.................starrrtttt (4-5sec) feels first loads only filter subscription, only then begins to load the browser itself
its really annoying

celeron 2.4 (sandy)

There are 2 approaches to this problem, and there are going to be two groups of people, either in favor of one or the other:

1. ABL 3.0 method, which loads the filter subscriptions after the browser has started and will start filtering "whenever it's ready". This will leave the browser open to load and display ads that you would normally block until it decides its done loading and setting up the filters.
2. ABL 3.5 method, which loads your filter subscriptions and filters upon browser startup. This prevents any loading and display (and connections to ad servers) for blocked content, but obviously will delay the browser's start until it is done setting up its rules.

Even in the land of the original Adblock Plus, people asked for method 2 when the dev changed the approach to be method 1.

I clearly understand that if you close and re-open the browser regularly, that this delay can become annoying, and the only workaround I can suggest at this point is to use a lighter-weight blocker like µblock.

I'm hoping Tobin can find the time to re-visit ABL 3.0 to make it compatible with Pale Moon v27, or maybe someone else can chip in and see if they can help out. I've not been involved with the development of either version of ABL so I can't really help here.

Moonchild wrote:

1. ABL 3.0 method, which loads the filter subscriptions after the browser has started and will start filtering "whenever it's ready". This will leave the browser open to load and display ads that you would normally block until it decides its done loading and setting up the filters.
2. ABL 3.5 method, which loads your filter subscriptions and filters upon browser startup. This prevents any loading and display (and connections to ad servers) for blocked content, but obviously will delay the browser's start until it is done setting up its rules.

Hey, Moonchild, thanks a lot for this explanation! It's now too much easier to understand how the old and the new version of ABL work.

Personally, since I'm running both Pale Moon 26.5.0 & Pale Moon Portable 27.0.1 from a SSD, the difference of startup times is really, really minimal. In the case of Pale Moon 26.5.0 is nuts!

So, after your explanation, I understand the ABL 3.5's method is better for privacy but I can't imagine the startup timing impact over traditional HDDs… I really hope Tobin can significantly enhance ABL in the near future.

Again, thanks a lot for this exposition!

Moonchild wrote:There are 2 approaches to this problem, and there are going to be two groups of people, either in favor of one or the other:

1. ABL 3.0 method, which loads the filter subscriptions after the browser has started and will start filtering "whenever it's ready". This will leave the browser open to load and display ads that you would normally block until it decides its done loading and setting up the filters.
2. ABL 3.5 method, which loads your filter subscriptions and filters upon browser startup. This prevents any loading and display (and connections to ad servers) for blocked content, but obviously will delay the browser's start until it is done setting up its rules.

Even in the land of the original Adblock Plus, people asked for method 2 when the dev changed the approach to be method 1.

I clearly understand that if you close and re-open the browser regularly, that this delay can become annoying, and the only workaround I can suggest at this point is to use a lighter-weight blocker like µblock.

I'm hoping Tobin can find the time to re-visit ABL 3.0 to make it compatible with Pale Moon v27, or maybe someone else can chip in and see if they can help out. I've not been involved with the development of either version of ABL so I can't really help here.

Thanks for the explanation, I can live with it. You could consider a splash screen, at least people see what's going on and have the assurance Pale Moon is indeed loading. Paint Shop Pro comes to mind, it takes quite some time to load and the splash tells you what it's loading.

All that said, thank you very much for you hard work on this wonderful browser I use every day.

Jottum

KNTRO wrote: but I can't imagine the startup timing impact over traditional HDDs…

Jottum wrote:Thanks for this, unfortunately it didn't solve the problem for me. Since installing version 27 (27.01 now) Pale Moon is slow (I mean sloooow ) at start up. Since there's no splash screen, one has no idea if Pale Moon is really starting or not. Compared to version 26 it takes about three times longer to load. Although a bit annoying, I can live with it. If this is a common experience, others (new users) might not be so understanding.

For the record, both on my Windows 7 and Kubuntu machine the behavior is the same.

Edit: Timed startup, from clicking the icon to interface show: 16 seconds.

HTH
Jottum

Well I did the jump to 27.0.1 myself and I found something interesting:

1. I got installed both versions 3.0 and 3.5 at once and they mess each other work.
2. My lists got corrupted.
3. I couldn't add elements to my block list

The solution I found was:

1. Uninstall 3.0 then reboot
2. Uninstall 3.5 then reboot
3. Disable ADB element hiding add-on then reboot
4. Clear cache just in case
5. Install 3.5 with EasyList then reboot
6. Enable ADB element hiding add-on then reboot

Things seem back to normal so far. I hope this works.

lobocursor wrote:Well I did the jump to 27.0.1 myself and I found something interesting:

1. I got installed both versions 3.0 and 3.5 at once and they mess each other work.
2. My lists got corrupted.
3. I couldn't add elements to my block list

The solution I found was:

1. Uninstall 3.0 then reboot
2. Uninstall 3.5 then reboot
3. Disable ADB element hiding add-on then reboot
4. Clear cache just in case
5. Install 3.5 with EasyList then reboot
6. Enable ADB element hiding add-on then reboot

Things seem back to normal so far. I hope this works.

Thank you for that lobocursor, indeed one has to remove version 3.0 before installing 3.5. I've followed your instructions and unfortunately all it proved is that it is 100% sure ABL is the culprit (Not that I doubted that). Without it Pale Moon starts in 2 seconds ­ with it - after the uninstall/reboot - it's back to 16 seconds after reinstalling ABL on my machine.

Other then the delay ABL is causing, I'm very pleased with version 27.01, it seems to be overall faster than 26.

Jottum

Switch to uBlock Origin. I did, problem solved.

I was going to say that same thing. uBlock Origin works with Aplomb (except on some Facebook groups' photo galleries there is a weird page reloading issue). But otherwise it works great!!!

Since I've decided for the present not to upgrade to PM 27.*, can anyone suggest a way to download ABL 3.0.3.1? I'm currently using 3.0.2, which I had stored on my computer.

PM extensions archive: ftp://archive:get@ftp2.palemoon.org/extensions/
(see also post by Moonchild here)

Thanks Coffeebreak. Got it bookmarked now.

I'm quickly getting frustrated with the startup delay with ABL 3.5 as well (and that's on my dev machine...) but I don't know enough about ABL or bootstrapped extensions to do anything about it.

I'm hoping someone can either:

• Look at ABL 3.0 and make it compatible with Pale Moon 27, OR
• Create a fresh fork off of ABP 2.8.2 which should work with our platform (being it states that it works with Firefox/Fennec 38.0 and above) -- since it's GPL3 licensed, this should be no problem.

EDIT: never mind, I think I already figured it out. I can revive 3.0 in a v27 compatible way, myself.

Moonchild wrote:
I can revive 3.0 in a v27 compatible way, myself.

Not to be pushy, but how soon will we see this available?