Jump to content

My Browser Builds (Part 1)


Recommended Posts

PM28, WinXP

My CPU had been racing on several web pages.  I tried several things, which eventually led me to rebuild my browser from scratch.  In doing so, I wished to run two instances of the browser, and used the command switches -profile <path> --no-remote.

To my surprise, my CPU issues went away, I guess because of the use of --no-remote.

Link to comment
Share on other sites


27 minutes ago, 404notfound said:

Ublock seems to fail spontaneously and stop filtering altogether with FF 55-based Basilisk

because ub0 tries to use more "modern" WE APIs that SP55 doesn't afford in later builds(IIRC ~1.18+).

Link to comment
Share on other sites

@404notfound Everything is working as expected here:

7mFVYGC.jpg

uBlock0-legacy v1.16.4.11 installed from GitHub: 

https://github.com/gorhill/uBlock/releases/tag/firefox-legacy-1.16.4.11

But the main thing to consider is that Serpent 55.0.0 on the Moebius platform can still connect to AMO (addons.mozilla.org) to check for extension updates, where St55 poses itself as Firefox 55.0; in reality, St55 has been forked from Firefox 53.0a1 and its WebExtension support is even inferior to stock Fx 53.0 (!). 

By default, St55 will update the legacy v1.16.4.11 of uB0 to v1.17.4 of the WE type, which, unfortunately, depends on WE APIs not (enabled/)found in Moebius (as pointed out by @roytam1), hence the issue you report...

The way to workaround this has been posted many a times in this thread, by several members, including both me and @Mathwiz : install (from GitHub) the companion extension called uBlockOrigin Updater:

https://github.com/JustOff/ublock0-updater/releases

IzVeqRa.jpg

Its action is two-fold:

1. Thwart Serpent 55 from making uB0 (extension) update calls to AMO (so it won't peak the incompatible WE version)

2. Keep an eye on uB0's GitHub repository for the appearance of an updated "legacy" version and either auto-install it or notify/prompt the user to install manually (according to user preferences).

Hope it's all clear now :P

 

Edited by VistaLover
Link to comment
Share on other sites

Without uBlock Origin Updater, Serpent 55 (Moebius) will self-update to 1.18.4 (or possibly later); Serpent 52 (and FF 52.9) will self-update to 1.17.4*.

Surprisingly, the new versions mostly work with Serpent (& FF), but there are a few features that don't, presumably due to WE APIs missing in versions before FF 55. For example, in the Dashboard / Settings / Privacy, the "Prevent WebRTC from leaking local IP addresses" setting is greyed out.

So I stick with the so-called legacy version (1.16.4.11), use uBlock Origin Updater to keep me there, and am able to check that privacy setting.

 

*Digression: it is possible to run uBO 1.18.4 with Serpent 52/FF 52.9, but several hoops must be jumped through (more on FF than Serpent), and since 1.16.4.11 works better anyhow, I don't feel it's worth the effort.

Link to comment
Share on other sites

54 minutes ago, Mathwiz said:

Without uBlock Origin Updater, Serpent 55 (Moebius) will self-update to 1.18.4 (or possibly later);

Not according to tests I conducted prior to my reply above...

Steps to reproduce:

1. Start with a new pristine Serpent 55 profile, using latest binary package offered by Roy:

basilisk55-win32-git-20190622-c2dfff698-xpmod.7z

2. Manually install

https://github.com/gorhill/uBlock/releases/download/firefox-legacy-1.16.4.11/uBlock0.firefox-legacy.xpi

k3aiB1q.jpg

3. Switch to Addons Manager (about:addons) tab, select the entry for uB0 1.6.4.11 and manually check ONCE for updates (right-click => Find updates); it will get updated first to 1.17.4 (WE):

ph9p0Nd.jpg

4. On the uB0 1.17.4 AOM entry now, just check again manually for an update; this time you won't be offered an additional update to a higher version; these have been my findings under Vista SP2 x86, where St55's default UA is

Mozilla/5.0 (Windows NT 6.0; rv:55.0) Gecko/20100101 Goanna/4.0 Firefox/55.0 Basilisk/20190622

NCUic5N.jpg

5. If I let Serpent 55.0.0 (new clean profile with only uB0, v1.6.4.11 manually installed and afterwards manually updated to v1.17.4) stay open but idle for a duration of, say, 15min, by coming back at it I find it has auto-updated to latest (AMO) v1.21.2:

hNLz8q1.jpg

NB that 1.21.2 is totally broken on Moebius under that test profile,, without even a glimpse of a toolbar button (not even in "Customize" mode); the dashboard, accessible via about:addons => uB0 => Options, is totally empty, too...

So, one's tests with uB0 WE on Moebius is probably a case of YMMV :angry:

Link to comment
Share on other sites

23 hours ago, mraeryceos said:

PM28, WinXP

My CPU had been racing on several web pages.  I tried several things, which eventually led me to rebuild my browser from scratch.  In doing so, I wished to run two instances of the browser, and used the command switches -profile <path> --no-remote.

To my surprise, my CPU issues went away, I guess because of the use of --no-remote.

Any side effects?

Link to comment
Share on other sites

23 hours ago, mraeryceos said:

I guess because of the use of --no-remote.

Highly unlikely :P ; you rebuilding your browser profile from scratch was what probably fixed your CPU issues (possibly some conflicting extensions/preferences/about:config settings were the cause of elevated CPU cycles in your original profile...).

FWIW, --no-remote is just a cmd line switch that means "don't talk to an existing Firefox, start a new instance"; together with the -p switch, one is able to launch a new Firefox (or fork) instance loading the specified profile, so that the two Firefox instances one ends up with are completely separated!

For anyone that cares, there exists an excellent article dedicated to the switch in question, found here :)

Link to comment
Share on other sites

20 hours ago, VistaLover said:

Highly unlikely :P ; you rebuilding your browser profile from scratch was what probably fixed your CPU issues (possibly some conflicting extensions/preferences/about:config settings were the cause of elevated CPU cycles in your original profile...).

FWIW, --no-remote is just a cmd line switch that means "don't talk to an existing Firefox, start a new instance"; together with the -p switch, one is able to launch a new Firefox (or fork) instance loading the specified profile, so that the two Firefox instances one ends up with are completely separated!

For anyone that cares, there exists an excellent article dedicated to the switch in question, found here :)

No.  Because I ended up continuing to use the browser profile without rebuilding it from scratch :-)  So as far as I can tell, given I made no other changes, it is the only reason.

The only side effect to using the switch, is that I can't launch a link in my browser from another application.  I will eventually remove the switch to see if it is reproducible, but right now, I'm too much enjoying my browser running so smoothly.

Edited by mraeryceos
Link to comment
Share on other sites

New build of Serpent/UXP for XP!

Test binary:
Win32 https://o.rths.cf/basilisk/basilisk52-g4.4.win32-git-20190803-3170ee769-xpmod.7z
Win64 https://o.rths.cf/basilisk/basilisk52-g4.4.win64-git-20190803-3170ee769-xpmod.7z

source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom

NM28XP build:
Win32 https://o.rths.cf/palemoon/palemoon-28.7.0a1.win32-git-20190803-3170ee769-xpmod.7z
Win64 https://o.rths.cf/palemoon/palemoon-28.7.0a1.win64-git-20190803-3170ee769-xpmod.7z

Official repo changes since my last build:
- Issue #1156 - Location Bar Preferences Checkboxes (93ceb8281)
- Merge pull request #1200 from flewkey/master (a4584c732)
- Update SQLite to 3.29.0 (154532072)
- Hide and disable open_all/cut/copy/delete/properties when opening bookmarks/history context menu with no selection (3170ee769)

Link to comment
Share on other sites

New build of BOC/UXP for XP!

Test binary:
MailNews Win32 https://o.rths.cf/boc-uxp/mailnews.win32-20190803-211bb28-uxp-3170ee769-xpmod.7z
Browser-only Suite Win32 https://o.rths.cf/boc-uxp/bnavigator.win32-20190803-211bb28-uxp-3170ee769-xpmod.7z

source patch (excluding UXP): https://o.rths.cf/boc-uxp/boc-uxp-src-xpmod-20190720.7z

No Official repo changes since my last build.

For UXP changes please see above.

Link to comment
Share on other sites

New New Moon 27 Build!

32bit https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190803-23551d191-xpmod.7z
32bit SSE https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190803-23551d191-xpmod-sse.7z
32bit noSSE https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190803-23551d191-xpmod-ia32.7z

64bit https://o.rths.cf/palemoon/palemoon-27.9.6.win64-git-20190803-23551d191-xpmod.7z

source repo: https://github.com/roytam1/palemoon27

repo changes since my last build:
- import change from rmottola/Arctic-Fox:
 - Bug 1128001 - Workaround ANGLE DEPTH16 being DEPTH24_STENCIL8. (144bc3839)
 - Bug 1038839 - Use type information for alias analysis. r=jandem (7f562bcc2)
 - Bug 1141797. r=smaug. (6ac0692bd)
 - Bug 1143470 - Add BUG_COMPONENT to moz.build files in toolkit and xulrunner. r=gavin (3fee7e2d5)
 - Bug 1083344 - Add "allow" sandbox rules to fix mochitests on OSX 10.9 and 10.10. r=smichaud (40c3323a5)
 - Bug 1083344 - Tighten rules for Mac OS content process sandbox on 10.9 and 10.10. r=smichaud (a1102b817)
 - Bug 1151974 P1 Delay Cache Context start until previous Context has completed. r=ehsan (20598fa6a)
 - Bug 1130686 - Add test for service worker client.focus. (e4d836af7)
 - Bug 1151916 - Set worker principalinfo on cache load. r=bkelly (4d55b31fe)
 - Bug 1139513 - Warn and gather data if ServiceWorker hits max workers per domain limit. r=bent, r=rvitillo (44c59a9cb)
 - Bug 1148354 - Deprecate the doppler effect from the PannerNode. r=ehsan (6de4e13ca)
 - Bug 1148942 - Ensure that the registration of empty service workers succeeds; r=bent (edbb09fdf)
 - Bug 1148496 - Allow to set an interface member as [Deprecated] in WebIDL. r=bz,smaug (43f554139) (23551d191)

Link to comment
Share on other sites

New regular/weekly KM-Goanna release:
https://o.rths.cf/kmeleon/KM76.2-Goanna-20190803.7z

Changelog:

Out-of-tree changes:
* update Goanna3 to git e48fcd77f..23551d191:
- import change from rmottola/Arctic-Fox:
 - Bug 1128001 - Workaround ANGLE DEPTH16 being DEPTH24_STENCIL8. (144bc3839)
 - Bug 1038839 - Use type information for alias analysis. r=jandem (7f562bcc2)
 - Bug 1141797. r=smaug. (6ac0692bd)
 - Bug 1143470 - Add BUG_COMPONENT to moz.build files in toolkit and xulrunner. r=gavin (3fee7e2d5)
 - Bug 1083344 - Add "allow" sandbox rules to fix mochitests on OSX 10.9 and 10.10. r=smichaud (40c3323a5)
 - Bug 1083344 - Tighten rules for Mac OS content process sandbox on 10.9 and 10.10. r=smichaud (a1102b817)
 - Bug 1151974 P1 Delay Cache Context start until previous Context has completed. r=ehsan (20598fa6a)
 - Bug 1130686 - Add test for service worker client.focus. (e4d836af7)
 - Bug 1151916 - Set worker principalinfo on cache load. r=bkelly (4d55b31fe)
 - Bug 1139513 - Warn and gather data if ServiceWorker hits max workers per domain limit. r=bent, r=rvitillo (44c59a9cb)
 - Bug 1148354 - Deprecate the doppler effect from the PannerNode. r=ehsan (6de4e13ca)
 - Bug 1148942 - Ensure that the registration of empty service workers succeeds; r=bent (edbb09fdf)
 - Bug 1148496 - Allow to set an interface member as [Deprecated] in WebIDL. r=bz,smaug (43f554139) (23551d191)

* Notice: the changelog above may not always applicable to XULRunner code which K-Meleon uses.

A goanna3 source tree that has kmeleon adaption patch applied is available here: https://github.com/roytam1/palemoon27/tree/kmeleon76

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

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