Pale Moon is an open source web browser forked off from Firefox, focusing on efficiency and ease of use, by leaving out unnecessary features, making optimizations, and having a fully customizable user interface, while maintaining compatibility with many Firefox extensions as well as its own extensions and themes.
Pale Moon provides a familiar set of controls and visual feedback similar to previous (pre-Australis) versions of Firefox, including grouped navigation buttons, a bookmarks toolbar that is enabled by default, tabs next to page content by default, and a functional status bar.
This is a third party build; the original project is at www.palemoon.org. For support, check out forum at http://forum.palemoon.org.
- Optimized for modern processors (SSE2)
- Based on the source code of Firefox
- Unnecessary bloat (social API, accessibility features, WebRTC) removed
- Support for Firefox extensions (add-ons) and themes
- More customization and configuration options than Firefox
This is what every other browser should have, a stripped down version alternative. Palemoon is fast and is breathing new life into my aging computers. It would be good to have it on OSx.
I want to thank all the folks who recommended Pale Moon. I’ve just been fed the f**h up with FF because of all of the memory leaks, etc. I've been running v16 forever because whenever I’ve tried to upgrade to newer versions, they’d all pretty much just crash after 30 minutes of heavy use, and not a single version of FF that I’ve ever used has ever fixed the memory leak problems. Not a single one. I actually installed a tiny batch file on quicklaunch so I could quickly kill FF at the point it’s consumed all of my RAM so I could then start over with “Restore Session” to automatically reload all of my previous tabs. After trying every “solution” to the leak problem, that’s the only one that ever did in any good for me. Apparently the arrogant tards at mozilla would rather tweak the UI to death rather than make a browser that actually works. They’re worse than even Microsoft because Microsoft has to listen to their customers sooner or later or go broke. Nonprofits can just drift along forever. At any rate, I just finished installing PM, including importing everything from FF with their little importer program, and everything went flawlessly, including all settings and the plethora of add-ons I use. The only difficulty was getting roboform attached, which I can’t live without. I did finally dumb around and got the roboform taskbar program to attach roboform to PM, which then worked flawlessly. It is, however, necessary for the roboform taskbar program to run all time for roboform to continue to work on PM, but this is a small price to pay to ditch FF forever. I've used PM for a week now, opening/closing/keeping hundreds of tabs, and I’ve been stunned at how much faster PM is than FF, as well as the VERY small memory footprint occupied by PM vs FF. Even after a week's HEAVY utility, PM has not grown beyond 1 GB, and even better, when I close tabs, ALL of the RAM is given back. Basically, PM is what FF ought to be, and even better, the genius behind Pale Moon, Mark Straver, has committed to keeping the PM UI fundamentally unmolested. I’ll be installing PM instead of FF on all of my client’s computers in the future as well!
Hi, I only use PaleMoon since FF Australis what about a ppa for updates? P.S. very good work
A perfect browser: fast, no crashes. Replaced Seamonkey with Pale Moon on Puppy Linux.
I installed Palemon for linux, but when I did open it and try to select anything I received this message : palemoon (process:12180): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed (pale moon:12180): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::sm-connect after class was initialised (pale moon:12180): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::show-crash-dialog after class was initialised (pale moon:12180): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::display after class was initialised (pale moon:12180): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::default-icon after class was initialised ###!!! ABORT: X_CreatePixmap: BadAlloc (insufficient resources for operation); 4 requests ago: file /home/a2g/pmsrc/toolkit/xre/nsX11ErrorHandler.cpp, line 157 ###!!! ABORT: X_CreatePixmap: BadAlloc (insufficient resources for operation); 4 requests ago: file /home/a2g/pmsrc/toolkit/xre/nsX11ErrorHandler.cpp, line 157 Segmentation fault So I tried a solution around and on the forum look like the problem is oxygen-gtk2 themes. So I changed on gtk2-qt and its working fine. My question is : its a palemoon's bug or a gtk2's bug?