Jump to content

Recommended Posts

Posted
3 hours ago, soggi said:

Hey roytam1,

is it possible to make New Moon 28 work better and add the grey border of the tabs again?

Here are screenshots of the 0516 and 0606 release of New Moon 28 (32-bit/SSE2) together with task manager and all 9 visible tabs (PCGamingWiki to EPoX EP-7KXA) loaded after exactly 5:00 minutes, nothing other has been changed except starting NM28. As you can see the 0516 release took 2:59 minutes and the 0606 release took 3:59 minutes CPU time (33 % more) on a dual core in those 5:00.

kind regards
soggi

NewMoon28_0516_5min.png

NewMoon28_0606_5min.png

for border issue, it could be https://repo.palemoon.org/MoonchildProductions/UXP/issues/3088

others are security related patches and I can't find which cause the slowness.


Posted (edited)

Here's a quick status update on New Moon 28 (32-bit) (2026-06-04) - the current release - under Windows XP running on a single-core 32-bit P4 with 1.5 GB of RAM. I have installed 25 extensions in my profile, 23 of which are enabled, 17 UC.JS scripts, 1 UC.XUL script, 4 USER.JS scripts, and 4 CSS stylesheets. When I launch the browser, it uses 184 MB of RAM, and it takes only a few seconds to load. My browser console shows no errors when the browser starts. If error messages appear, they are caused by websites. :P The reason for this is that New Moon 28 runs smoothly out of the box – at least as far as the browser console is concerned, thanks to @roytam1 – and I wrote my UC.JS scripts on the premise of running completely error-free. And regarding  extensions I either fixed faulty ones myself or, if unfixable, I removed them. :)

Edited by AstroSkipper
Update of content
Posted (edited)

The only real issue that all browsers in single-process mode as, for example, New Moon 28, have – and which has always been the case with every version of Firefox – is their inability to free up RAM when tabs are unloaded or closed. The amount of memory that is actually released is pitiful compared to the amount that was originally used. It’s a problem that has remained unresolved since the very beginning, so to speak. :o And these days, developers no longer worry about wasting RAM, because most of them have plenty of it. But my Windows XP computer doesn't. :P
What is particularly pleasing, however, is that GitHub has been running smoothly in New Moon 28 for some time now and, as far as I can tell, is actually running very well at the moment. :thumbup

Edited by AstroSkipper

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...