My Browser Builds (Part 5)

[roytam1]

1 minute ago, johk said:

And you know what they say, that if you play with fire your end burning yourself.

Well I got a BSOD (I didn't have one since a couple of years) when testing the 20260425 build in safe mode.

I send the dmp minidump privately to you @roytam1 as I think it might have some personal information.

if you get a BSOD normally means a hardware or driver problem rather than software/browser problem.

[Ben Markson]

Here's a new mystery. This is using the latest SP52 v52.9.0 (2026-04-24) (32-bit).

I'm in the process of testing a ZTE MC888A 5G router and you access it's UI from http://192.168.0.1/index.html – fine.

However, if I do this from XP I get this error:
 ReferenceError: isErrorObject is not defined . . . http://192.168.0.1/service.js

If I do it from W7, no error, no problem.

This is using the exact same version of SP52 and the exact same profile on both computers.

How can that happen?

 

Solved: It was a dirty cache caused by sharing the same address as the wired router.

Ben.


(The UI does work using MyPal under XP so it's not something inherent to the XP OS)
 

Edited April 26 by Ben Markson

[AstroSkipper]

@roytam1 For ages one permanently gets error messages regarding the absence of the favicon.ico file in the root directory of  your server o.rthost.win when visiting. Would it be possible for you to put one there? That would make my browser console look a lot less red. And if you can fix it that easily, it should be done in seconds. I would be delighted in any case. Of course, it's up to you. Just a polite request.

Edited April 27 by AstroSkipper

[johk]

16 hours ago, roytam1 said:

if you get a BSOD normally means a hardware or driver problem rather than software/browser problem.

Ok, you are the programmer :)

But it was very coincidental that at the same time NewMoon freeze, I went to try to close it and BSOD :S

Anyway, I won't use the 20260425 build as, for whatever reason, gives me problems.

[VistaLover]

On 4/25/2026 at 9:43 PM, johk said:

... and now it hangs on loading github notifications...

The latest build is, by far, slower on my Core2Duo CPU.

If it's anything to go by, my own CPU on my Vista SP2 x86 laptop is a Core2 Duo from late 2007 (Intel Core2 Duo CPU T5250 @1.50GHz, "Merom") ; this can go up to the SSSE3/EM64T instructions set...

[j7n]

I used to get BSOD, which, I suspect, surfaced because the browser stressed the HDD by saving many files to its cache, also maybe in conjuction with using video aceleration at the same time. So I can't say the browser was at fault, but that it exposed some problem.

[FelixPls1]

the lightning calendar extension seems to be broken on the latest mailnews

[roytam1]

25 minutes ago, FelixPls1 said:

the lightning calendar extension seems to be broken on the latest mailnews

you may need to grab lightning xpi and change install.rdf with `<em:strictCompatibility>false</em:strictCompatibility>`

[AstroSkipper]

Today, I have updated to New Moon 28 (20260418) and I can also confirm that GitHub websites are running much better than in older releases. As mentioned in previous posts, I will avoid using the release 20260425.

[AstroSkipper]

On 4/26/2026 at 4:20 PM, AstroSkipper said:

@roytam1 For ages one permanently gets error messages regarding the absence of the favicon.ico file in the root directory of  your server o.rthost.win when visiting. Would it be possible for you to put one there? That would make my browser console look a lot less red. And if you can fix it that easily, it should be done in seconds. I would be delighted in any case. Of course, it's up to you. Just a polite request.

@roytam1 Thanks for uploading a dummy favicon.ico file to your server o.rthost.win! 

[modnar]

I also downgraded to 4-18 release of Serpent 52.9. On imgur.com it just stopped responding after going through a few posts.

BSOD that some mentioned could also be because of excessive fragmentation the browser causes with its cache on disk. I remember long time ago (2013) I had the same problem with fireferret.

[roytam1]

next build will change parse-thread count from core-count*4 to core-count - 1 to see if this helps.

if not, it will further reduce back to single parse-thread later.

[VistaLover]

On 4/27/2026 at 6:06 PM, roytam1 said:

and change install.rdf with
`<em:strictCompatibility>false</em:strictCompatibility>`

This is the exact workaround suggested in 

https://github.com/martok/palefill/issues/109

in the case of PaleFill-1.30.xpi NOT installing by default in latest UXP browsers like NM28/St52...

I have conducted a small investigation  and it appears that this started happening with last week's UXP releases; with 

"palemoon-28.10.7a1.win32-git-20260411-d849524bd-uxp-c8f7030b13-xpmod",

latest palefill can be normally installed from GitHub in NM28; but, starting with 

"palemoon-28.10.7a1.win32-git-20260418-d849524bd-uxp-d4c4c1f6ec-xpmod"

the extension won't directly install, because the browser thinks the XPI is incompatible: 

So, we have a "regression" window, "c8f7030b13...d4c4c1f6ec"; is this new behaviour deliberate or a UXP bug? Do you think you can identify which UXP change made extensions requiring "strictCompatibility" incompatible with UXP builds >= 20260418 ? 

Thanks in advance for any insight; and, as ever, thanks for all those efforts of yours  ...

[roytam1]

17 hours ago, roytam1 said:

next build will change parse-thread count from core-count*4 to core-count - 1 to see if this helps.

if not, it will further reduce back to single parse-thread later.

upstream tested and it needs to be reverted. https://forum.palemoon.org/viewtopic.php?p=272957#p272957

[roytam1]

9 hours ago, VistaLover said:

This is the exact workaround suggested in 

https://github.com/martok/palefill/issues/109

in the case of PaleFill-1.30.xpi NOT installing by default in latest UXP browsers like NM28/St52...

I have conducted a small investigation  and it appears that this started happening with last week's UXP releases; with 

"palemoon-28.10.7a1.win32-git-20260411-d849524bd-uxp-c8f7030b13-xpmod",

latest palefill can be normally installed from GitHub in NM28; but, starting with 

"palemoon-28.10.7a1.win32-git-20260418-d849524bd-uxp-d4c4c1f6ec-xpmod"

the extension won't directly install, because the browser thinks the XPI is incompatible: 

So, we have a "regression" window, "c8f7030b13...d4c4c1f6ec"; is this new behaviour deliberate or a UXP bug? Do you think you can identify which UXP change made extensions requiring "strictCompatibility" incompatible with UXP builds >= 20260418 ? 

Thanks in advance for any insight; and, as ever, thanks for all those efforts of yours  ...

I was thinking if it is caused by https://github.com/roytam1/UXP/commit/ae7c40d4611542893882b2a3ea5d739852962734