When my browser starts acting funny like what you're describing, what I do is -

1. Help --> Troubleshooting Information --> Refresh PaleMoon. This should clear out all the miscellaneous junk (and all your add-ons too, alas!). This works most of the time.
2. If that fails, you could export your bookmarks as an html file and rm your user settings.

Admittedly these are draconian measures, but desperate times...

Hope this helps!

1 members found this post helpful.

This time I chose to compile from source 27.8.1, everything so far seems stable and as snappy, I do not notice any significant lag; and of course GTK2 is still working (another plus), unlike Firefox. No regrets dumping FF for PM.

Works fine here, built with alsa, gtk2. system-libvpx ..
Could be startup cache, there is ~/.cache/$mozvendor/$mozapp/$profile or something like that.
Maybe keep track of all your settings in user.js then you can move that file to a clean new default profile.

1 members found this post helpful.

There is new version 27.8.3 (source)
Apparently, the bug which caused the browser to crash on certain websites, is now fixed.
It never crashed here, but I've read some bug reports and assumed javascript malfunction.

So Pale Moon v27.9.0 released this morning, and apparently the 27.9.x series will be the last of the Goanna 3.4 builds.

Pale Moon v28.x.x forward will be Goanna 4.1 and the UXP platform.

From the release notes:
An interesting (but confusing to me) side note: https://forum.palemoon.org/viewtopic...138924#p138924

3 members found this post helpful.

I've been building and testing out alpha builds of Pale Moon 28.x.x and I'm very excited about it. This will bring a lot of great improvements to Pale Moon. I think all the modern browsers, Chrome, modern FireFox, are rather ugly; and although I think the most recent addition of FireFox improved that somewhat, its still remains largely ugly. Also, I dislike the direction modern browsers are headed. With, Pale Moon, however, we're getting to cherry pick some of the improvements that have happen on the back end of modern browsers, without heading down the same failed path, they appear to be going down.

3 members found this post helpful.

Pale Moon

27.9.1 (2018-05-07)
This is a maintenance release.

Changes/fixes:
Removed the unused/incomplete places protocol handler.
Worked around an issue with MSE media without a Track ID. This should help with the playability of some live streams.
Ported across jemalloc improvements from UXP.
Ported across cairo mutex improvements from UXP.
Added support for FFmpeg 4.0/libavcodec 58.
Added a fix for Windows 10's "isAlpha()" not being what one would expect in v1803.

2 members found this post helpful.

Well, the Pale Moon team has decided to add NoScript to a "Level 1" status addon and apparently means that an addon is "known to cause security OR stability issues". Link

It has been stated that it causes "stability" issues with the browser. I have only seen that it breaks websites because it blocks scripts, which is exactly what is intended.

Personally, I have seen NO issues where NoScript has caused stability issues with the Pale Moon browser itself. I actually think that adding NoScript to the blocklist is a security breach in itself. Everyone knows that scripts can potentially be malicious or track users among other things. I don't think that this is the right path that the Pale Moon team have taken, but I am just a enduser and have no say one way or another.

Now if you have NoScript installed you will recieve a pop-up and you will have to actively UNTICK the radio box and click "Restart Later".

NoScript will continue to work as normal if you do that. Otherwise you will need to go into your add-ons page and re-enable NoScript.

Further, they started getting a bunch of negative feedback about adding NoScript to the blacklist so they decided to lock the thread and ended up banning one of their own team members (he was their web dev I think) I'm assuming for comments he made in the Pale Moon forum due to adding NoScript to the blacklist.

IMO this may be a little bit of overreach, because if it is only breaking websites and not the browser itself, then it is working exactly as intended. For users that want the opposite, ie; allow all scripts unless you block them (makes no sense to me) there is YesScript.

2 members found this post helpful.

I've been test-using Pale Moon 27.8.3 on my everyday-use Slackware64 14.1 laptop to see if it's suitable for use, abusing it in ways that I wouldn't normally treat my browser.

Yesterday it finally crashed, after 34 days of use.

That's marginally less stable than Pale Moon 25.6.0, which consistently stays up for 45+ days, but then I was also being deliberately unkind to it to uncover any problems.

From this trial I've drawn the tentative conclusion that 27.8.3 is stable and useful. It also has noticeably better html5 support than 25.6.0, which makes it better-suited to crazy interactive webapps like facebook and mewe.

2 members found this post helpful.

???

I'm using Pale Moon 27.9.1

Where have you been?

Pale Moon 28.x.x is going to be built on a new engine and the UXP platform so all your testing might be for naught.

1 members found this post helpful.

I've been on 25.6.0.

My testing demonstrated that the version being tested (27.8.3) might be suitable for use.

Of course it demonstrates nothing about other versions, especially later versions. That is just the nature of the beast.

When 28 comes out, it will be tested and judged on its own merits.

If your point is that it takes longer to test software than it takes the dev team to whip out new versions of that software, your point is well taken. The decision to use the latest release vs a tested release is a matter of individual preference.

You have to take into consideration that there have been security and other fixes. I don't think that Pale Moon, or any other software would be around very long if they are not "suitable for use".

That is absolutely true.

For every software project, some releases are better than others.

Even when a dev team has a good track history, as Pale Moon's does, sometimes a release simply isn't up to snuff.

It's not possible to know which versions are good, and which are less-good, until someone gives them a good hard use.

Some people don't care, and will just trust that any version will be good, or accept the occasional glitchy release as a normal part of the user experience.

There is nothing wrong with that. Different people have different standards.

My post was to just to let people know that I had given 27.8.3 a good hard reaming-out and it held up well. It's one of the good releases. That does not imply that other releases are bad.

If that's not useful to you, fine. It just means you weren't part of the intended audience.

Can we just drop it, already? I feel like a minor misunderstanding over a trivial FYI has set off a powder keg.

2 members found this post helpful.

I think you will be impressed with Pale Moon 28 series ttk, fwiw.

1 members found this post helpful.