AstroSkipper

Good comparison! This clearly shows the positive effect of rebasing I stated in previous posts. 66.6% less RAM consumption. That's a lot. BTW, maybe your CPU is weaker (I can't remember what kind of CPU you have) but your system is equipped with 4 GB RAM, mine with only 1.5 GB RAM (slow SD-RAM, i.e., no DDR-RAM).

In my system with 1.5 GB RAM, every single megabyte counts. 350 to 450 MB is then a huge amount of RAM.

Didn't you just contradicted yourself? This flag only has an effect if you are TAB HOARDING !!! No. If you open two or three tabs of the same domain to really work with them, then this has nothing to do with tab hoarding as they are closed immediately when all is done.

Personally, I consider opening 15 MSFN tabs and probably many more tabs from other websites to be tab hoarding. IMHO, this kind of surfing behaviour might require professional treatment. BTW, I used to be afflicted with this disease for a while, but fortunately, as an autodidact, I was able to free myself from it. As for the chrome flag --process-per-site, I use it from the beginning and it really saves RAM. I consider this flag useful.

And now, all in a minimal, quite fresh profile of Mypal 68.14.4b in multiprocess mode, only one empty tab open, 3 extensions installed with 1 enabled, no themes installed, 1 UC.JS script enabled, no CSS stylesheets enabled, xul.dll file rebased and memory minimisation performed. The RAM usage is then round about 120 MB a few minutes after starting the browser: I am generally interested in RAM usage values of other users to see how Mypal 68.14.4b behaves on different computers. And of course, I am particularly interested in comparative values under Windows XP 32-bit on old, weak computers such as mine.

Mypal 68.14.4b in multiprocess mode, only one empty tab open, 25 extensions installed with 17 enabled, 2 additional themes installed with one of them enabled, 13 UC.JS scripts enabled, 13 CSS stylesheets enabled, xul.dll file rebased and memory minimisation performed. The RAM usage is then round about 250 MB a few minutes after starting the browser: What is yours?

I see it like this. If websites can't be loaded properly on my old computer under Windows XP, it's a sign that this website has disqualified itself for my system and now has the pleasure of making the acquaintance of my Android tablet. BTW, websites that take up hundreds of megabytes of RAM are simply rubbish in my world. Especially if they waste my precious RAM to show ads, offer meaningless things and collect user data.

Contrary to my original statement, I have tried to open the Facebook website in Thorium. Even there I am rewarded with a 100% CPU load, and my free RAM memory is being eaten up. The only thing that allows the page to load is using a mobile user agent. Unfortunately, many elements are then not displayed correctly. So, it remains the same. The FB page is just rubbish.

Facebook as well as all these social media sites have become overbloated more and more day by day and year by year. I've just logged in an old FB account in Mypal 68, and the RAM eating started. Only my FB front page open, and Mypal 68 consumes 750 MB. I won't test this crappy service in Thorium as there is not enough RAM for such bad sites. I think such social media sites are more made for mobile devices the last years. On Android, there are corresponding apps for each of these services. Personally, I do not use these services. And I hate them all.

It should be mentioned at this point that I do not use uBO Legacy 1.16.4.35 at factory defaults. I use a different set of filter lists than the default one. Furthermore, I use additional lists, own rules and scripts. The initial, default setting is only a basic one and is not YouTube related. And I didn't get a video ad on the second video.

But now that various theories have been put forward about YouTube and overlay pop-ups with warnings to the user, I am happy to put forward my theory, which I will not verify or prove in any way. Google, and therefore YouTube, wants to make money. If users use the service over a long period of time without being a premium customer and yet without getting and watching any adverts, then this will certainly be registered by YouTube and therefore by Google in whatever way. These users must then have been using an adblocker the whole time and will eventually receive this overlay pop-up warning.

You didn't say that in this post. You only talked about a certain number of videos. Now suddenly, it's the duration. Somehow I get the feeling that these are just unsubstantiated theories and nothing more. But YouTube is a crappy interface and no option for browsers on my system. I use YouTube itself only on my Android tablet. Anyway! Opening videos via the legacy extension uTube is much, much, much better than the original YouTube interface. So, I am not interested in investigating the YouTube interface in UXP browsers.

I tried your first playlist in the most recent version of New Moon 28 using the legacy extension uTube and my mod uBlock Origin Legacy with several filter lists enabled. No such overlay popup after playing 8 and more music videos.

Yep! And they still work with my mod uBlock Origin Legacy. Why do you post an ad blocker for Chrome in a thread about legacy extensions for UXP browsers? Same applies to this extension. Not compatible with UXP browsers. Such recommendations should be done in corresponding threads. Otherwise it would be misleading. TBH, I have never seen such a message. I tried to reproduce your issue but I failed,. It doesn't seem directly related to the video in your screenshot. Here is my screenshot with your video in New Moon 28: No problem to play this video apart from the unfortunate fact that the music is terrible, which is of course always a question of taste.

You're welcome.

@Tomcat76 A JavaScript solution for your problem with hiding the tab bar, if only one tab is open, can be found here: https://msfn.org/board/topic/183657-mypal-68-in-windows-xp-custom-buttons-and-extensions/?do=findComment&comment=1271917

HideTabbarWithOneTab In my download archive, I found an old but still working UC.JS script called HideTabbarWithOneTab.uc.js. This script hides the tab bar including the Open a new tab button, if only one tab is open, and shows it again, if a further tab is loaded. According to its author the script is based on the extension of the same name. Since Firefox 23, the tab bar can no longer be hidden if only one tab is open. This script solves this problem. In contrast to many pure CSS implementations as recently discussed in another thread starting from this post, it works perfectly in Mypal 68. The HideTabbarWithOneTab.uc.js file has to be copied in the Mypal's profile subfolder chrome. It has been tested by me and is fully working. Here is a short animated GIF file to show the script in action: Requirements: The package MYPAL_68_CB_requirements.7z from the first post of this thread. Download link: https://www.mediafire.com/file/r84j3z9krrqxzks/HideTabbarWithOneTab.uc.js/file

Personally, I am not really interested in running legacy extensions in Mypal 68. I am more interested in working UC.JS scripts and CSS stylesheets. But there was one legacy extension that I really wanted to get running and was finally able to install in Mypal 68 long time ago. It's the legacy Custom Buttons extension. Here is a screenshot: The advantage in using legacy custom buttons in Mypal 68 is that they are not restricted in their actions as, for example, webextensions unfortunately are. Legacy custom buttons just do what their JavaScript code commands them, whatever that may be.

Ok. I can confirm that your code is indeed working except hiding the Open new tab button when only one tab is open. My recommendation is to move the Open new tab button to another toolbar, for example to the left of the url bar or to the right of the search bar, via the toolbar menu entry Customize. Doing so, this code is enough: /* Hide single tab -- works */ tab:only-of-type{display:none !important;} /* Reduce the minimum height of the tab bar to 0 so that it collapses when empty -- works */ #tabbrowser-tabs, #tabbrowser-arrowscrollbox, #tabbrowser-tabs > .tabbrowser-arrowscrollbox{min-height:0 !important;} The moved Open new tab button does no longer cause wasting of screen space. Another solution without the need of moving the Open new tab button will be posted by me, too.

No. Unfortunately, this code is not effective. It does totally unnecessary things. Look at my posted screenshots! My code is working as it should. Furthermore, you didn't provide any information what you did. Thus, I can't help you.

@Tomcat76 I don't think your CSS code, which you didn't post here, is able to hide the tab bar, if only one tab is open, and immediately show it again when opening an additional tab, all in the same browser session. For that, you need a script which checks the state of the tab bar in the background by an observer function. AFAIK, this can't be done with CSS but with JavaScript. Edit: I have to correct a bit my statement above. In the special case of hiding the tab bar, when only one tab is open, it can be partially done in Mypal 68 even with CSS, as shown in the following post.

Then, you did something wrong. Check all steps again! All files have to be copied into the correct folders. And check if all modified prefs have been assigned to the correct values via about:config! Don't forget to delete the startup cache in the profile folder before you restart your browser! You have to start Mypal 68 with the profile where the chrome folder was created, of course. One thing is clear. All was tested in depth and is working. And my CSS code, too. BTW, re-posting what I wrote in my instructions is not helpful. I definitely know what I did. You should better post what you exactly did. And provide screenshots of all relevant folders' content and your userchrome.css! This is the only way I can help you.

From a programming point of view, this is a condition. If there is only one tab, then hide the tab bar with the New Tab button. If there is more than one tab, then do not hide Tab Bar with the New Tab Button. Something like this should rather be realised with a JavaScript UC.JS file created inside the profile's chrome folder.

Hello @Tomcat76 If unresponsive script errors come back, do what I already posted: If you manually moved the New Tab button away from the tab bar by drag & drop, then try this code: #new-tab-button { display: none !important; } If you didn't move it, i.e. the button is still located on the tab bar, then try this code: .tabs-newtab-button.toolbarbutton-1 { display: none !important; } Both CSS codes were tested by me on my system and definitely work in Mypal 68.14.4b. Cheers, AstroSkipper

This is interesting, please elaborate how to select the value? The drawback is about this too, more memory hungry and then crash even if you have it free left Rebasing is not a panacea. But I have had great experiences with rebasing the chrome.dll file in the 360Chrome browser. On my hardware, I was able to solve a BSOD problem caused by another programme and reduce the RAM memory consumption by more than half. Whether rebasing is necessary or useful depends on how the corresponding DLL files are compiled. Keyword: ASLR. If a browser such as Mypal 68 consumes too much RAM, I always experiment with rebasing the main DLL file, in this case the xul.dll file. However, the base address of 0x6af00000 is a default address selected by the tool libase if this is not changed in its INI config file by the user. Here is the command line command for rebasing with the tool libase: libase xul.dll And here is the content of my libase.ini file: [Generated bases] 62a00000=CHROME.DLL 6da00000=CHROME_CHILD.DLL 6af00000=XUL.DLL 63e00000=ICU63.DLL For a DLL file in Windows, the default base address is 0x10000000 for 32-bit images. After a research in the internet, the most suitable address range for DLLs is from 0x60000000 through 0x6f000000. Microsoft proposes to reduce the range further to 0x60000000 through 0x68000000 in order to accommodate with MIPS processors, too. Another tool for rebasing is Microsoft's Rebase which is part of the Microsoft Windows SDK for Windows 7 and .NET Framework 4. Here is the command line command for rebasing with the tool Rebase:: rebase -b 0x6af00000 xul.dll However, it is a game of trial and error to check, whether rebasing has an effect, and to find a suitable base address. Experience to date has shown that Mypal 68 is stable and uses slightly less RAM when the xul.dll file has been rebased. No crashes here. At least, on my hardware when using Mypal 68 in multiprocess mode. I remember something was done already in extension, the question is the minimize memory thing useful at all. I already mentioned that I use a legacy custom button for this purpose which can be seen in the top right of my posted screenshot. I marked it with a red arrow. In multiprocess mode, a not inconsiderable amount of wasted RAM memory can thus be reclaimed on a regular basis. This has already been tested by me. Therefore, I would like to see such a feature natively implemented in Mypal 68, as I described in my previous posts.