Jump to content

My Browser Builds (Part 1)


Recommended Posts

New build of BOC/UXP for XP!

Test binary:
MailNews Win32 https://o.rths.cf/boc-uxp/mailnews.win32-20190511-b487656-uxp-1b5c261b8-xpmod.7z
Browser-only Suite Win32 https://o.rths.cf/boc-uxp/bnavigator.win32-20190511-b487656-uxp-1b5c261b8-xpmod.7z

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

Official repo changes since my last build:
- [PLATFORM] Update commit pointer (b487656)

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-20190511-3a87e4659-xpmod.7z
32bit SSE https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190511-3a87e4659-xpmod-sse.7z
32bit noSSE https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190511-3a87e4659-xpmod-ia32.7z

64bit https://o.rths.cf/palemoon/palemoon-27.9.6.win64-git-20190511-3a87e4659-xpmod.7z

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

repo changes since my last build:
- import change from rmottola/Arctic-Fox:
 - more pointerstyle to apply patches (bfb888a02)
 - Bug 1144331 - Assert that gray buffering does not depend on isMarking (775d1d6b3)
 - Bug 1144789 - Strongly type GrayBufferState enum and move to GCRuntime (48db96a71)
 - pointer style (8e1f6b47f)
 - Bug 1144794 - Move markBufferedGrayRoots to the GCRuntime (82a65b5d4)
 - Bug 1144811 - Inline the start and end buffering gray roots methods on GCMarker (e5fa2fa45)
 - Bug 1144817 - Move hasBufferedGrayRoots to GCRuntime (360528a61)
 - Bug 1144832 - Move grayBufferState manipulation out of GCMarker (aae607d5b)
 - Bug 1144834 - Move resetBufferedGrayRoots to GCRuntime (c80e490e3)
 - Bug 1144920 - Move gray buffer clearing out of GCMarker (99495ce33)
 - Bug 1144925 - Buffer gray roots using a CallbackTracer instead of the GCMarker (faae3bca3)
 - Bug 1144931 - Move gray buffering code to RootMarking.cpp (c279e36bd)
 - Bug 1144369 - Add a GC phase to track time spent buffering gray roots (e05c2eece)
 - Bug 1142669 part 1 - Fix inliningMaxCallerBytecodeLength to return the correct value. (d5e4d1a84)
 - Bug 1129977 - Fix bogus MarkOffThreadNurseryObjects assert when post-barrier verifier is used. (4d204fb5e)
 - pointer style (8a3a7e129)
 - pointer style (f6db66131)
 - Bug 1142669 part 2 - Lower the script inlining size limit if off-thread compilation is not available. (ce4e3c5e6)
 - Bug 1142669 part 3 - Limit the total inlined bytecode size to avoid excessive inlining. (a57fab6e2)
 - Bug 1142669 part 4 - Fix some inlining issues and inline scripts with loops. (777fb2ec6)
 - Bug 1142669 followup - Move OffThreadCompilationAvailable definition outside namespace block. (c4fd10799)
 - Bug 1142669 part 5 - Lower inliningMaxCallerBytecodeLength from 10000 to 1500. (9f1c704a2)
 - pointer style (d70a2a7be)
 - Bug 1144743 part 1. Add a hasPollutedGlobalScope flag to scripts. (da965507f)
 - Bug 1144743 part 2. Add an option to JS::CompileOptions for hasPollutedGlobalScope. (df6324dd4)
 - Bug 1144743 part 3. Set hasPollutedGlobalScope when we're compiling scripts we know will be executed with a non-global scope without cloning them. (c2f264683)
 - Bug 1144743 part 4. Set the hasPollutedGlobalScope flag correctly when compiling functions. (39fff6585)
 - Bug 1144743 part 5. Set the hasPollutedGlobalScope flag correctly when cloning functions. (738f1d18a)
 - Bug 1144743 part 6. Set the hasPollutedGlobalScope flag correctly when executing scripts. (b05d04d63) (d3e5fc8cf)
- ported from UXP: backport m-c 1510114: Fix Use-After-Free in the HTML5 Parser (3a87e4659)

Edited by roytam1
Link to comment
Share on other sites

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

Changelog:

Out-of-tree changes:
* update Goanna3 to git 249ad075c..3a87e4659:
- import change from rmottola/Arctic-Fox:
 - more pointerstyle to apply patches (bfb888a02)
 - Bug 1144331 - Assert that gray buffering does not depend on isMarking (775d1d6b3)
 - Bug 1144789 - Strongly type GrayBufferState enum and move to GCRuntime (48db96a71)
 - pointer style (8e1f6b47f)
 - Bug 1144794 - Move markBufferedGrayRoots to the GCRuntime (82a65b5d4)
 - Bug 1144811 - Inline the start and end buffering gray roots methods on GCMarker (e5fa2fa45)
 - Bug 1144817 - Move hasBufferedGrayRoots to GCRuntime (360528a61)
 - Bug 1144832 - Move grayBufferState manipulation out of GCMarker (aae607d5b)
 - Bug 1144834 - Move resetBufferedGrayRoots to GCRuntime (c80e490e3)
 - Bug 1144920 - Move gray buffer clearing out of GCMarker (99495ce33)
 - Bug 1144925 - Buffer gray roots using a CallbackTracer instead of the GCMarker (faae3bca3)
 - Bug 1144931 - Move gray buffering code to RootMarking.cpp (c279e36bd)
 - Bug 1144369 - Add a GC phase to track time spent buffering gray roots (e05c2eece)
 - Bug 1142669 part 1 - Fix inliningMaxCallerBytecodeLength to return the correct value. (d5e4d1a84)
 - Bug 1129977 - Fix bogus MarkOffThreadNurseryObjects assert when post-barrier verifier is used. (4d204fb5e)
 - pointer style (8a3a7e129)
 - pointer style (f6db66131)
 - Bug 1142669 part 2 - Lower the script inlining size limit if off-thread compilation is not available. (ce4e3c5e6)
 - Bug 1142669 part 3 - Limit the total inlined bytecode size to avoid excessive inlining. (a57fab6e2)
 - Bug 1142669 part 4 - Fix some inlining issues and inline scripts with loops. (777fb2ec6)
 - Bug 1142669 followup - Move OffThreadCompilationAvailable definition outside namespace block. (c4fd10799)
 - Bug 1142669 part 5 - Lower inliningMaxCallerBytecodeLength from 10000 to 1500. (9f1c704a2)
 - pointer style (d70a2a7be)
 - Bug 1144743 part 1. Add a hasPollutedGlobalScope flag to scripts. (da965507f)
 - Bug 1144743 part 2. Add an option to JS::CompileOptions for hasPollutedGlobalScope. (df6324dd4)
 - Bug 1144743 part 3. Set hasPollutedGlobalScope when we're compiling scripts we know will be executed with a non-global scope without cloning them. (c2f264683)
 - Bug 1144743 part 4. Set the hasPollutedGlobalScope flag correctly when compiling functions. (39fff6585)
 - Bug 1144743 part 5. Set the hasPollutedGlobalScope flag correctly when cloning functions. (738f1d18a)
 - Bug 1144743 part 6. Set the hasPollutedGlobalScope flag correctly when executing scripts. (b05d04d63) (d3e5fc8cf)
- ported from UXP: backport m-c 1510114: Fix Use-After-Free in the HTML5 Parser (3a87e4659)

* 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

On 5/8/2019 at 1:51 AM, mockingbird said:


I'm getting this crash when launching the 64-bit version in XP x64.  Any advice please?

palemoon3.png.60c7a1874b4365a81c13958671c2caca.png

I tried it with a new, clean profile as well.

Thank you.

please try latest build if it still crash or not.

Link to comment
Share on other sites

On 5/11/2019 at 1:18 PM, Slavich said:

Language packages from the official site of Pale Moon are not established on two last modifications of New Moon 28 XP mode.

... This has been already previously covered many a times in this thread ;) ; in the case of New Moon 28, which is built from code on the UXP master branch, you shouldn't be using the official language packs destined for officially released stable Pale Moon versions: 

http://addons.palemoon.org/language-packs/

Instead, one should install the most up-to-date pack offered at @JustOff's GitHub repository:

https://github.com/JustOff/pale-moon-localization/releases

(at the time of writing, 28.6.0_RC1 is the most current release); if the installed LP becomes incompatible with a new NM28 release, one has to disable it (via Safe Mode, if browser won't start at all) and thus return to the default en-US GUI, until such time as an updated LP becomes available in the linked GitHub repo (or, if you're qualified, try to fix it yourself by looking at "*/locales/en-US/*" string changes in the official GitHub changelog and then porting these to your installed package...).

:)

Link to comment
Share on other sites

Thanks, VistaLover

 

I had one problem with reflection of a font on some websites. On a font of the text zachka appear. Such problem is also in Firefox 52.

There is an add-on for correction of such malfunction?

u_b67b3ce45dadccd73423e925ec0f7506.jpg

Edited by Slavich
Link to comment
Share on other sites

... And despite all recent incidents involving Mr. Matt A. Tobin and Moonchild Productions in general, there still exist people who post in the official Pale Moon forums questions related to Feodor2's MyPal and @roytam1's New Moon forks:

https://forum.palemoon.org/viewtopic.php?f=4&t=22110

These "people" are only doing a disservice to the XP and Vista communities benefiting from the continued existence of these forks and they must be stopped from continuing such an infantile and foolish behaviour; the only unwanted effect they'll cause is more aggravation for the MCP devs, more hostility towards the maintainers of the forks and their users!

Who in his/her right mind would go to the official Pale Moon community (devs+users) forum and query about third-party "unsupported" forks running on OSes that the mere mention of their names would cause those people to throw a hissy fit? Please, anyone here with a PM forum account (I know several exist) contact that @DJboutit individual and try to talk some sense into him/her :realmad: . We can't risk any additional animosity from the upstream devs :(!

Link to comment
Share on other sites

14 minutes ago, VistaLover said:

... And despite all recent incidents involving Mr. Matt A. Tobin and Moonchild Productions in general, there still exist people who post in the official Pale Moon forums questions related to Feodor2's MyPal and @roytam1's New Moon forks:

https://forum.palemoon.org/viewtopic.php?f=4&t=22110

These "people" are only doing a disservice to the XP and Vista communities benefiting from the continued existence of these forks and they must be stopped from continuing such an infantile and foolish behaviour; the only unwanted effect they'll cause is more aggravation for the MCP devs, more hostility towards the maintainers of the forks and their users!

Who in his/her right mind would go to the official Pale Moon community (devs+users) forum and query about third-party "unsupported" forks running on OSes that the mere mention of their names would cause those people to throw a hissy fit? Please, anyone here with a PM forum account (I know several exist) contact that @DJboutit individual and try to talk some sense into him/her :realmad: . We can't risk any additional animosity from the upstream devs :(!

This user is obviously a moron, but who cares? I assume Pale Moon is GPL'd, right? If so, they can't do anything about others forking, and redistributing their browser. Regardless of how annoyed they may be.

 

Yeah, nevermind what I just said lol.

Edited by sparty411
Link to comment
Share on other sites

10 hours ago, VistaLover said:

... And despite all recent incidents involving Mr. Matt A. Tobin and Moonchild Productions in general, there still exist people who post in the official Pale Moon forums questions related to Feodor2's MyPal and @roytam1's New Moon forks:

https://forum.palemoon.org/viewtopic.php?f=4&t=22110

These "people" are only doing a disservice to the XP and Vista communities benefiting from the continued existence of these forks and they must be stopped from continuing such an infantile and foolish behaviour; the only unwanted effect they'll cause is more aggravation for the MCP devs, more hostility towards the maintainers of the forks and their users!

Who in his/her right mind would go to the official Pale Moon community (devs+users) forum and query about third-party "unsupported" forks running on OSes that the mere mention of their names would cause those people to throw a hissy fit? Please, anyone here with a PM forum account (I know several exist) contact that @DJboutit individual and try to talk some sense into him/her :realmad: . We can't risk any additional animosity from the upstream devs :(!

I could do it but I won't.
And excuse me Vistalover for this if I do not collect your request.:no:
Users of that forum are very rude, misguided and prejudiced.
They have the donkeys they deserve.:thumbdown

Sorry again.

Link to comment
Share on other sites

https://o.rths.cf/boc-uxp/
BNAV Browser (RT)

https://addons.thunderbird.net/en-US/seamonkey/addon/metal-lion-sea-monkey/versions/
https://addons.thunderbird.net/eN-US/seamonkey/addon/metal-lion-silver-sea-monkey/versions/
These two (above URLs) Metal Lion SM Themes (Original, Silver) can be easily made to install.
Each one has an ACTIVE TAB with a different (brighter) color -- nicely done.

Use 7-ZIP software to unZIP the *.xpi THEME files to a folder, then edit the INSTALL.RDF file.
Then reZIP all files, and name it again as XPI file for installation.
This 'coding' below must be added (nested appropriately) to INSTALL.RDF near file bottom:

*** Note: the 'minVersion' setting (below) got corrected, due to necessity ***

<!-- RT BNAV Borealis Navigator (below) -->
        <em:targetApplication>
            <Description>
                <em:id>{a3210b97-8e8a-4737-9aa0-aa0e607640b9}</em:id>
                <em:minVersion>0.1.0a1</em:minVersion>
                <em:maxVersion>*</em:maxVersion>
            </Description>
        </em:targetApplication>
<!-- RT BNAV Borealis Navigator (above) -->

Just carefully locate (nest) the 'coding' above and SAVE the INSTALL.RDF file.
Thanks to MSFN.org users 'VistaLover' and 'RoyTam1' for help on INSTALL.RDF editing.

https://msfn.org/board/topic/177125-my-build-of-new-moon-temp-name-aka-pale-moon-fork-targetting-xp/page/101/?tab=comments#comment-1158936
(About RT BNAV Browser and LANGUAGE PACK installation)

Edited by TechnoRelic
Link to comment
Share on other sites

I have just tried the newest version of Firefox 45 ESR SSE (45.9.15) on my Pentium III RDD, and compared to the older versions, I noticed that scrolling in webpages appears to be choppier, less smooth than it is for example on New Moon 27 and the older versions of FF45 ESR SSE. To make sure it wasn't an impression of mine, I rolled back to 45.9.14 and the latest stable version, 45.9.11, and I've indeed noticed that the older versions are way smoother when scrolling websites, even with pictures (especially after applying the UOC Patch). I noticed that in 45.9.15, when I scroll a website with pictures that are loading, the scrolling noticeably lags, while in the older versions it scrolls almost seamlessly when pictures are loading, at least with the UOC Patch enabled. I hope this choppy scrolling issue can be addressed and eventually fixed, as I've currently rolled back to 45.9.11, which behaves as fine as 45.9.14 on my machine. A big thumbs up to @roytam1 for his great work, and I hope my report can be useful. :)

Edited by looking4awayout
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...