Leaderboard

@Sampei.Nihira for the 13857163618319817th time gave an article, a very dubious one, even the author wrote he didn't check himself. When asked, @Sampei.Nihira didn't provide any proof of what he claims (as usual), instead he told Karla to trust his word (as usual, in a rude form) . At least today he didn't write to "shut up". As for the topic, there's a tracking app in Supermium/Thorium, it's an old Googel invention, we (You, Dixel and I) axed it off 360 and Chrome a long time ago.

Don't you dare to "period" members, especially women. Evidently, you didn't read the article you yourself linked to. "This has been around since at least 2016." My solution from 2013 is different, and I explained it in details (with the screenshot). People just don't trust you word anymore, you've been caught too many times posting disinfo, misleading articles and so on. I posted the screenshot, what stops you to do the same? The author of the article wrote "should", it's all in theory. "The question has arisen that in this case, the extension should be blocked – but I have not tested this." Of course, because the author suggested a very dubious way to block via GPO, which resets when one starts a new profile! Why didn't you mention that? Huh?

It's there at least from 2013, I knew about it all along, wrote about it on the forum (along with @Dixel), and I always deleted it from resources.pak, all of those "methods" to use "policies" are crap. chrome will revert all those. The only way is to cut it out physically. Screen from the latest CentBrowser, as an example.

@ED_Sln use --disable-component-update https://github.com/win32ss/supermium/issues/829

Chrome doesn't request those to be present on any OS.

I'd start with removing outdated VC redist packs, they are known to cause issues, on XP especially. If you ever had them, remove all remnants. I don't install those at all.

Hello, folks! Either of you get this message when using third party downloaders? Simply playing one video at a time, I don't get this message, so it's not related to IP. Details. https://github.com/yt-dlp/yt-dlp/issues/10128

Intrusion Prevention System.

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

I don't even have to login anymore, they just let me in. Everyone knows D.Draker.

He's talking about this (below pic) INPUT BOX. Mine will look different than yours because I heavily customize via a userstyle sheet here at MSFN. But "however" you log in, there will be TWO input boxes - one for EMAIL ADDRESS and the other for PASSWORD. It didn't used to be EMAIL ADDRESS for the first of two input boxes, IT USED TO BE USERNAME - and there was no "forum announcement" for this change, it just "happened one day".

No, it's not related to login verification where you would receive an e-mail with a link to click on in order to verify it's you. Nothing like that at all. It's about the username and password fields when you're logged out and you want to log back in. You could previously either type in your e-mail address or your display name as the username. While now you can only type in your e-mail address as your username, but not the other. That's the change that was made. I do have a static IP, or public IP rather, and I use a router. I have several of both actually. It's not so difficult to change my public (and static) IP address, but I would have to give my ISP a call. Not as easy as release and renew, but it's workable. I have some public services running from my home. I always figured why only use one half of the Internet service I pay for, for accessing external resources, when I can do the opposite and serve up resources for others to use, including myself. But running servers and services from your home is becoming less common these days. Most people don't know how to do that. But even the techies shy away due to the risks involved by exposing your network to the Internet. But Internet would not be Internet without at least two interconnected networks. The Internet landscape has changed for the worse over the years though, with dark forces lurking around every node. So I do understand people who are perfectly happy with putting their Internet connection devices behind a CGNAT and then host their services with a professional server/VPS provider. (I do that too.)

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.

What kind of drawback is it? @feodor2 Any information on that? @feodor2 Actually, this was a feature request. Any opinion on this?

It is because Chrome won't let you. But then again, it's there - regardless. And the "method" to detect it, whaht they suggest, of course does't work.

Eventually, everything's comes to an end, I too saw win32 promised to look into newer drivers and so on, doesn't look like it will happen, sadly. Yes, too much time already passed.

Yes, GenAHCI should work on Windows 7, just remove MSHDC driver before integration in Components -> Drivers -> IDE ATA/ATAPI controllers. Then integrate it on Drivers page.

What kind of drawback is it? The last weeks, I had been using Mypal 68.14.3b, and all in all, I couldn't observe any serious problems. Today, I have updated to Mypal 68.14.4b. I should mention at this point that I use all your releases with an xul.dll file rebased on the base address of 0x6af00000 to try to improve the terrible memory hunger of Mypal 68. As a further and quite effective measure, especially in multiprocess mode, I automatically perform every 10 minutes a memory minimization by a legacy custom button. In this way, I free Mypal 68 from occupied RAM memory (and that's not even that little) that it does not want to release on its own, even though it no longer needs it. I wonder if such a feature could be optionally implemented in Mypal 68 under the Options → Performance tab, i.e. a checkbox with an input field to minimize memory every x min where x is set by the user. In the end, this would automatically call up the already existing minimize memory function, which all Firefox browsers natively have, periodically. In any case, Mypal 68 (and thus Firefox) must be restricted as far as RAM consumption is concerned. Especially on old, weak computers that are only equipped with a small amount of RAM.

Disable hardware acceleration as a test to see if eBay tabs still crash or not! Check all relevant settings regarding hardware acceleration in about:config! Especially media and codecs related ones. Tab crashes are very often related to the hardware acceleration as reported by users. Of course, there may also be other reasons. Check also your graphics card drivers and all related settings! Furthermore, try to block on eBay as much as possible by uBlock Origin! And provide your hardware specs regarding CPU, RAM and graphics card, and the used OS! PS: All test should be done in a brand new and clean profile to ensure that the used profile isn't faulty.

No. Actually, these crashes can't be related to these two prefs settings. I use both for a longer time and didn't notice any tab crashes. TBH, I have never seen this messsge before. This must be caused by someting different. And the crappy eBay website doesn't work well in Mypal 68 for some time. I did an order on eBay yesterday using Mypal 68, and it wasn't a pleasure. You should use uBlock Origin in any case especially if accessing such bloated websites. Do you use Mypal 68 in single- or multi-process mode? Do you use a new, clean profile? Please provide more detailed information when posting issues!

The "Purge all caches" button was unfortunately removed when releasing uBlock Origin 1.55. I love it when useful, tried and tested features are simply removed, for whatever reason. Here is a link: https://github.com/gorhill/uBlock/releases/tag/1.55.0 The good is, in my special mod uBlock Origin Legacy which of course isn't compatible with Mypal 68, it will stay forever. But this is another story.

This didn't work for me.

We all here agree with everyone, most of the time. I think the reason is - he can't run 122. Perhaps, and most likely, the user is on XP. I always loved how 360 was super fast, let it rest in peace. Thorium is heavier, btw.

Yep, but as soon as it again can't render, all gets back to IE. Had it many times in the beginning of 2023, then I moved to another browser completely.

Like @Karla Sleutel puts it, any constructive suggestions?

Dave, don't know about other versions, in the most popular 1030 it ignores that setting at all. When the browser can't render the site properly, it tries to do it with IE mode, gets stuck.

I have installed all Microsoft Visual C++ Redistributable Packages up to the last XP-compatible version 2019. You can't really determine which packages are outdated or not as older programmes need very often older VC++ versions. And I don't think these package are responsible for the Thorium crashes as they all are also installed in my Windows XP Pro SP3 + POSReady partition. And there, all is fine.

TBH, so far I have been able to find and even fix every error in my Windows XP partitions. My personal statistics therefore clearly indicate that I will also eliminate this issue. The current, empirically obtained data from other users does not, of course, confirm my null hypothesis H0. As I said before, I am not willing to install POSReady updates in my Windows XP Pro SP3-only partition. So I need to take alternative options and investigate them in depth.

@NotHereToPlayGames You should not fall into the belief that @AstroSkipper is plagued by bias and narrow-mindedness. As a scientist and mathematician, it is a matter of course to open the mind in all directions. Hypotheses are made and either accepted or rejected. Assertions, on the other hand, have to be proven. Since I formulated the relation between Thorium crashes and the non-existence of POSReady updates in a Windows XP installation as a hypothesis from the outset, there is of course the possibility of accepting a hypothesis that is simply wrong, which is called an type II error in statistics. I made this clear from the very beginning. My investigations go in all directions. From the beginning, an alternative theory was that some loaded modules, programmes or drivers could be responsible for the Thorium crashes. I am investigating my problem in all possible directions as I always do.

But too much time-consuming, considering that we are talking about 365 updates, as I mentioned earlier, although I am also interested in the cause of these sudden closes. After a deep research in the internet, I found out that many users suffer from this Chrome issue and have switched to Firefox as there seems to be no real solution. If this error also occurs on my Windows XP Pro SP3 + POSReady partition, I will immediately give up Thorium.

Thorium is Chrome based. Search for the string " Chrome immediately closes when starting" or similar search strings, and you will see I am not the only one. My issue is a common error in Chrome. You should actually know that as a Chrome/Chromium fan.

Both partitions were created by me in 2004. Since then, there has been no reinstallation due to a perfectly functioning imaging system. I correct all errors myself. The registry of both have been modified, cleaned and fixed by myself. The main difference between them is that I had to stop the updating of Windows XP with the last update in 2014 in one of them, and in the other, I applied the POSReady hack and performed updating until 2019. PS: I never had an infection, which had to be removed by an antimalware programme, in both Windows XP installations. And don't forget there is an undetermined probability of type II error for accepting the null hypothesis H0.

Judging by the amount of typos in the OP's post, I think it's a typo. It's 1030. Also doesn't work for me.

You accused me of being "wrong" without proof, without providing any insight on why it works on Windows 10 with an old UA, or even the original one, like in the case with the member @66cats. https://msfn.org/board/topic/182304-extreme-explorer-360-chromium-78-86-general-discussion/?do=findComment&comment=1268986 And now you write "it seems you are seeking strife where none exists." Are you sure you didn't confuse me someone else? I'd like to get to the bottom of why it works on 10, but not XP, which is the topic. Got any problem with that? Ignore, then. My theory is the fingerprint the browser makes. Client Hints is one of the most possible culprits.

That's not what I meant, and you perfectly know it. I meant you spoofed to v.77 from a Windows 10 machine.

I wouldn't rely only on one site to test that "feature". Client Hints have been main stream since as early as January 2020. Before saying I'm "wrong", how then you'd explain the site works perfectly fine on Windows 10 and old UA?

Of course it would load on v.77 under Windows 10, the OS you've been running for a couple of years instead of XP.

New New Moon 27 Build! 32bit https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190713-2a3dd7f84-xpmod.7z 32bit SSE https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190713-2a3dd7f84-xpmod-sse.7z 32bit noSSE https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190713-2a3dd7f84-xpmod-ia32.7z 64bit https://o.rths.cf/palemoon/palemoon-27.9.6.win64-git-20190713-2a3dd7f84-xpmod.7z source repo: https://github.com/roytam1/palemoon27 repo changes since my last build: - import change from rmottola/Arctic-Fox: - Bug 1139453 - Send network UP/DOWN events on desktop Linux. (7466c1298) - Bug 1141488 - On non-APZ platforms, combine any async transform with the OMTA transform rather than clobbering it the OMTA transform. (fe48d6774) - Bug 1080752 - Hold wakelock when attempting to connect to push server. (b1e74295f) - Bug 1126089 - Allow messages to be sent after frame script unload event. (167ebbd9a) - Bug 1126089 - Add test for pageload event on browser element when tab closed (f2011e6e4) - Bug 1090921 - Logging to see which tasks remain alive too long (ebfc3c9bd) - Bug 1142544 - delete now-unnecessary |extern "C++"| block from nsISupportsUtils.h; r=mccr8 (07e6572f8) - Bug 1142503 - don't use QueryInterface when the compiler can do the cast for us; r=ehsan (b13219054) - Bug 1140161 - Sensibly handle patterns with absolute paths in TEST_HARNESS_FILES. (173e369a7) - Bug 1082510 - When we detect a chrome popup at the current event coordinates and remote content has the mouse captured, release capture. r=Enn (da9fe26a7) - Bug 1137722 - Ensure that system message cache is refreshed before openapp. r=fabrice (97dc41f50) - Bug 1139904 - Add initial test runtime files for mochitest browser-chrome and devtools (9837c79b1) - Bug 1061604 part.1 nsTextStore::GetTextExt() should rReturn previous character rect instead of TS_E_NOLAYOUT when Google Japanese Input retrieves first character of selected clause at composing r=emk (54779d30e) - Bug 1061604 part.2 nsTextStore::GetTextExt() should rReturn previous character rect of modified range instead of TS_E_NOLAYOUT when Google Japanese Input retrieves caret rect during composition r=emk (ba7f93879) - Bug 1136051 - component_insert_pair statrs checks only while we are still checking or haven't started pairing; (ae1ae1d4f) - Bug 1137007 - Detect namespace and SECCOMP_FILTER_FLAG_TSYNC support in SandboxInfo. r=kang, r=Unfocused (6d9e32a8f) - Bug 1142263 - Specify all syscall parameters when doing CLONE_NEWUSER detection; f=bwc r=kang (8bcba1831) - Bug 1142567 - Remove FAIL_ON_WARNINGS_DEBUG; It is not used. (bf22f1ccf) - No bug - Add an explanatory message to the multiple-inheritance assertion in DOM bindings; # (ffd94ef07) - Bug 1141252. Don't mark the TablePainter display item as having background-attachment:fixed content if the background-attachment:fixed image will be painted by a dedicated nsDisplayTableCellBackground. r=mats (98287b37c) - Bug 1140084 - delete list of script counts in tail-recursive fashion. (90a2b7c45) - Bug 1048741 - [WebGL2] texParameter: Fix silly bug in TEXTURE_COMPARE_FUNC handling. (ccc90dae3) - Bug 1142478. Fix integer attribute parsing to not lose track of leading zeroes. (d596a1ce1) - Bug 1139388 - Remove superfluous locking in the OS X profiler implementation to fix deadlock. (r=mstange) (a13088958) - Bug 1128603: Remove findReferences and the tests that use it. (bccc64734) - Bug 1140683: Fix async plugin init using null plugin funcs on MacOSX (47b591d54) - Bug 1142494 - Fix OSX packaging mistake. (15555f4ee) - Bug 1136784 - Add screenshot to LogShake produced data. (7ff264243) - Bug 1142550 - Fix screenshot. (d684b6469) - Bug 1142006 - Set MACOSX_DEPLOYMENT_TARGET earlier. r=mshal (c333b954e) - Bug 1100966 - Remember all ranges for all selections when joining nodes in the editor transactions; r=roc (bf34bd0c8) - Bug 1136507 - L8, LA8, and A8 should not be renderable. (96e807795) - Bug 1128019 - Init SCISSOR_BOX with initial width and height. (7258cc44c) - Bug 1142211 - Add layerization testing mechanisms to reftest. r=roc (4c6aa11f8) - Bug 1106905 - Modify mobile desktop mode implementation to use a desktop viewport. (644ede0e7) - Bug 1139675 - Simplify the APIs for getting and setting the pres shell resolution. r=mstange,mattwoodrow (c520a8c98) - Bug 1141563 - Don't update Shapes in parallel after compacting GC (098af79c9) (2a3dd7f84)

typo, its actually 1.1 the official "1.0" was never released publicly, only versions before which had no numbers at all

Yes, mailnews is supported.

OK corrected.

I updated my installer file to install the latest builds, AND i have a new version of my installer (v1.1) change log: added support for more browsers (it should install all of RT1's browsers now) coming soon: task scheduler support UOC patch support addon installation feature (maybe) as always, get it here: http://i430vx.strangled.net/files/XP/RoyTam Browser Installer.exe

New New Moon 27 Build! 32bit https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190706-0a2ee1ef2-xpmod.7z 32bit SSE https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190706-0a2ee1ef2-xpmod-sse.7z 32bit noSSE https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190706-0a2ee1ef2-xpmod-ia32.7z 64bit https://o.rths.cf/palemoon/palemoon-27.9.6.win64-git-20190706-0a2ee1ef2-xpmod.7z source repo: https://github.com/roytam1/palemoon27 repo changes since my last build: - import change from rmottola/Arctic-Fox: - Bug 1143192 Allow Context initialization to be cancelled. (e408a5854) - Bug 1140065 Check for null actor before using it in CacheStorageChild::RecvOpenResponse(). (3a5875d64) - Bug 1149987 - Part 5: Hold a kungfu death grip in FetchPut::MaybeNotifyListener; (60845a3ef) - Bug 1149987 - Part 6: Release the FetchPut object on the right thread in FetchObserver::OnResponseEnd(); (bf9172b17) - Bug 1109751 - Consume FormData support in Fetch API. (be2ea94d7) - Bug 1149987 - Part 8: Do not store or match Response objects with a Vary:* header; (1f5de94f6) - Bug 1126819 - Part 1: Respect the RequestInit.cache member in Request's constructor; (b11b19aee) - Bug 1126819 - Part 2: Persist the Request.cache attribute in DOM Cache; (31c2db054) - Bug 1147695 - Enable interception of beacons through service workers; r=nsm (899b62ecd) - Bug 1142727 - Do not intercept sandboxed iframes with service workers; r=nsm (fee4c2ae6) - Bug 982726 - Test the number of clients returned by matchAll. (c2c0b0b9b) - Bug 1147367 - Add a test for checking the Request.context attribute for FetchEvents generated for fetch(); (c93d28f40) - Bug 1147699 - Part 1: Move Request::mContext to InternalRequest, and determine the mapping to nsContentPolicyType; r=nsm (356433175) - Bug 1147996 - Enable interception of CSP reports through service workers; r=nsm (9c040e1d6) - bug 1147490 - fix GLContextProviderNull. (95dbbc863) - Bug 1137814 - nsAString and nsACString in URL.cpp/h (687d66aad) - Bug 931249 - patch 1 - Scriptloader use cache if needed. Bug 931249 - Patch 1.1 - Set baseURI when script is obtained from cache. (7ab055659) - Bug 931249 - patch 2 - cachename integration. (f84945f92) - Bug 931249 - patch 2.1 - reuse cache name between updating and installing worker. (bf1846186) - Bug 931249 - patch 2.2 - purge old active worker cache when activating new worker. (116a50da3) - Bug 1131271 - Set ServiceWorker script redirect limit to zero. (af8ae3444) - Bug 931249 - patch 3 - tests. (eb9769c2f) - Bug 931249 - patch 4 - comparison. (ba0b8c833) - Bug 931249 - patch 5 - set redirection limit back to zero. (4ff8f49f2) - Bug 931249 - Patch 4.1 - Fix addref/release declarations on Windows builds. (c58f55fe8) - Bug 931249 - Patch 6 - Fix abort condition in CompareCache::OnStreamComplete. (2054a1d8b) - Bug 931249 - Patch 7 - Call Done() after Succeed() when cache and network match. (31ec38719) - Bug 931249 - Patch 8 - Provide direct getter to the fact that we are loading a worker instead of relying on cache name. (e5f62b684) - Bug 931249 - Patch 9 - Use ServiceWorker cache name as part of it's unique name. r=khuey (d6481d3cd) - Bug 931249 - Patch 10 - Bypass HTTP cache when downloading ServiceWorker script to compare against. r=bkelly (6309eaf90) - Bug 931249 - Patch 11 - Remove unused cacheName. (33bf983c5) - Bug 931249 - Patch 12 - Call LoadingFinished even if channel is not present. r=khuey (2a868e45a) - Bug 931249 - Patch 13 - Fix finish condition in CacheScriptLoader::Fail. r=baku (0033bc2ab) - Bug 931249 - Patch 14 - kungfuDeathGrip. r=baku (8d112108b) - Bug 931249 - Patch 15 - assert later. r=baku (9eca21509) - Bug 931249 - Patch 16 - Keep ServiceWorker alive during installation steps. r=baku (307dbe265) (09883465b) - import change from rmottola/Arctic-Fox: - Bug 1094764 - Implement AudioContext.suspend and friends. r=roc,ehsan (79ff7e5ea) (and GraphDriver.cpp vc2013 fix from bug1163469) - Bug 1147699 - Part 2: Set the content policy type on FetchEvent.request based on the content policy type of the channel; r=nsm (f4bfbb8e2) - Bug 1147699 - Part 3: Add a test for FetchEvent.request.context when intercepting an image load; (36e429469) - Bug 1147699 - Part 4: Add a test for FetchEvent.request.context when intercepting a responsive image load; (c7f4a27f3) - Bug 1147699 - Part 5: Add a test for FetchEvent.request.context when intercepting an audio element load; (40dfbeb87) - Bug 1147699 - Part 6: Add a test for FetchEvent.request.context when intercepting a video element load; (dcc6a359a) - Bug 1147699 - Part 7: Add a test for FetchEvent.request.context when intercepting a beacon load; (8cb913bff) - Bug 1147699 - Part 8: Add a test for FetchEvent.request.context when intercepting a CSP report (67d7ab74a) - Bug 1147699 - Part 9: Add tests for FetchEvent.request.context when intercepting embeds and objects; (b7f8d3c11) - Bug 1147699 - Part 10: Add a test for FetchEvent.request.context when intercepting font loads; (4108db24e) - Bug 1147699 - Part 11: Add tests for FetchEvent.request.context when intercepting iframes and frames; (981c93483) - Bug 1147699 - Part 12: Add a test for FetchEvent.request.context when intercepting new window loads; (cd1ce857f) - Bug 1147699 - Part 13: Add a test for FetchEvent.request.context when intercepting ping loads; r=nsm (377e09600) - Bug 1146610 - Add static_asserts that check the validity of the enum values that we write into the cache database; r=bkelly (ac8c96abc) - Bug 1147699 - Part 14: Add a test for FetchEvent.request.context when intercepting loads coming from plugins; r=nsm (0e1769bb4) - Bug 1148064 - Enable interception of pings through service workers; r=nsm,smaug (8dc3328cb) - Bug 1150608 Do not reuse CacheId values within an origin. (4eb46f1d5) (acfadf1d4) - import change from rmottola/Arctic-Fox: - Bug 1142917 - add logs to GMPChild. (ba458fb52) - Bug 1124996 - Block S3TC on OSX 10.10 & HD3000. (907466fd4) - Bug 1142957 Fallback to main display CVDisplayLink if active displays aren't available. (02e155615) - Bug 1139049 - turn EnumRoleAccessible into template (4285a88c3) - Bug 1139049 - revert EnumRoleAccesisble name change (0bf9e3703) - Bug 1139576 - make accessible creation by tag name faster, (2aac035d6) - Bug 1139900 - make tag name based roles faster (dd3d1a00f) - Bug 1140497 - add more roles into markup map (f106edc6d) - Bug 1140500 - add object attributes declaration into markup map, (d50b288da) (49a83a24e) - import change from rmottola/Arctic-Fox: - Bug 1001634 - Add basic MathML accessibility implementation (bf5b4d740) - Bug 1139576 - New_ functions should be static (04f64cb93) - Bug 1142681 - Let CreateECParamsForCurve() assert a non-null arena parameter (d18f9f721) - Bug 1142863 - Remove unused struct RemoveQuotaInfo in dom/quota/QuotaManager.cpp. (e557fab3a) - Bug 1142860 - Remove unused exception parameter in osx_corewlan.mm. (a5fbc52c0) - Bug 1135543 - Part 2 (no part 1): Add a |metadata| parameter to CrashManager.addCrash() (c01dea4a3) - Bug 1135543 - Part 3: Create events file format crash.main.2 which contains metadata (3aa7f0dc1) - Bug 1135543 - Part 4: Define DailyCrashesMeasurement6 containing main-crash-oom; (Partial only, missing files in AF) (ea64fac70) - Bug 1143239: Add MOZ_OVERRIDE annotations in ClientReadbackLayer. (ac2608288) - Bug 1141858 - Fix error message for unexpected extended attribute on dictionary members. (c395919fd) - Bug 1142338 - Debugger.Memory's census shouldn't use JS::ubi::Node::as<T>; (e2e9eb767) - Bug 1139464 - In GetNearestScrollableFrame(), associate the root APZC with the root scroll frame of the root document (whether chrome or content), not the root content document. (9964d72bc) (0a2ee1ef2)

it seems that there is some minor ABI differences. Can you try redownloading the archive?

New New Moon 27 Build! 32bit https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190629-253db3c3f-xpmod.7z 32bit SSE https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190629-253db3c3f-xpmod-sse.7z 32bit noSSE https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190629-253db3c3f-xpmod-ia32.7z 64bit https://o.rths.cf/palemoon/palemoon-27.9.6.win64-git-20190629-253db3c3f-xpmod.7z source repo: https://github.com/roytam1/palemoon27 repo changes since my last build: - nss: update to 3.44.1, with vc2013 fix and gyp fix (0982e5a8d) - import change from rmottola/Arctic-Fox: - Bug 1087646 - Properly serialize nullprincipal URIs across IPC. (1fcc5a63e) - bug 1137538 - remove nsIIdentityInfo and nsNSSSocketInfo::GetPreviousCert Bug 1136471 - Remove unused nsIIdentityInfo.getValidEVPolicyOid(). (f23ed7a6f) - Bug 1049476 - 0001. webidl change - Support user certificate parameter (ba92ac3c6) - Bug 1049476 - 0002. Support user certificate parameter in API. (30ec1a9c8) - Bug 1049476 - 0003. Add EAP-TLS to wifi capabilities. (69920f968) - Bug 1130400. Part 1. Pass the passed in anchor frame to SetPopupPosition in nsMenuPopupFrame::LayoutPopup if we have one. r=enndeakin (2de244c51) - Bug 1130400. Part 2. Use a reflow callback to set the position of xul popups. r=enndeakin (aa2117085) - Bug 1130400. Add test. (9047c9013) - Bug 1043143: Step 2a: Add a class like nsDownloader but using memory instead of a file. (fad673f10) - Bug 1034143: Step 2b: Add the ability to read jar files from arbitrary memory. (e1dc9faa6) - Bug 1034143: Step 1: Fix tests for bug 945152 and bug 1008126. r=smaug (e6b6cc408) - Bug 1043143: Step 3: Convert nsJARChannel from temporary files to temporary memory. r=honzab (79e381e50) - Bug 1145631 - Part 1: Replace MOZ_OVERRIDE and MOZ_FINAL with override and final in the tree; r=froydnj (f21f630cb) - Bug 1148527 - Indentation fix after bug 1145631 (a8153b9c5) (b372a2634) - import change from rmottola/Arctic-Fox: - cleanup whitespace (402d7b83b) - Bug 1140658 - Part 7: Close underlying file stream in ReadStream before reporting closed; (2bce37716) - Bug 1143223 - Teach Cache ReadStream not to AddRef() itself in its destructor. (b262891bd) - Bug 1140658 - Part 1: Create a mini-framework for running tests in the worker, service worker and window contexts (ff56f6f4e) - Bug 1140658 - Part 2: Merge test_cache.js and test_cache_frame.html (b6eabb6fd) - Bug 1140658 - Part 5: Remove test_cache_quick_close.html because it makes no sense after bug 1131353 (19d0a7f24) - Bug 1142333 - Add a test for passing Request objects to DOM cache match methods (506346266) - Bug 1142790 - Add a test for passing Request objects to DOM cache matchAll method; (7629a098e) - Bug 1142269 - Auto-vacuum the DOM Cache database; r=bkelly (7918837f0) - Bug 1143959 - Set the journal mode and foreign key pragmas for all DBActions; r=bkelly (72203a916) - Bug 1143894 - Part 1: Clear the ErrorResult message if InternalHeaders::Get fails; r=bkelly (fd5afc218) - Bug 1143894 - Part 2: Support Vary headers including multiple header names in DOM Cache; r=bkelly (cb3d7129d) - Bug 1143894 - Part 3: Do not propagate errors in getting the headers to the outside world; r=bkelly (de058497a) - Bug 1143894 - Part 4: Add tests for handling of the Vary header in DOM Cache (bd174ede9) - Bug 1143894 - Part 5: Add a test for handling of the Vary header with multiple entries in the cache; r=bkelly (780cf31ce) - Bug 1142790 - Add a test for passing Request objects to DOM cache matchAll method; (318bacb44) - Bug 1140658 - Part 4: Port test_cache_add.html to the new mini-framework; (fbd80b0f6) - Bug 1142772 - Interleave the DOM Cache tests run through the mini-framework; r=bkelly (37c61b81f) - Bug 1143193 - Run the tests for match and matchAll on both Request objects and string URLs; (cb6a122f9) - Bug 1143219 - Add tests for passing an unknown request to match and matchAll; (6eed5fb13) - Bug 1143511 - Correct the usages of .catch() in DOM cache tests; r=bkelly (aa7fbd0f7) - Bug 1143813 - Add tests for attempting to store a non-GET request in the DOM Cache (573164971) - Bug 1143820 - Add tests to ensure that the URL fragments are correctly ignored by the DOM Cache API; (81c4bea52) - Bug 1143833 - Add tests for the ignoreSearch match mode in DOM cache; (013de8632) - Bug 1143222 - Avoid dumping out extremely long response bodies to the mochitest log, and re-enable the newly added DOM cache tests to run both in seqential and parallel modes; r=bkelly (be68c42b0) - Bug 1144337 - Add tests to ensure that cacheName is only honored on CacheStorage, and not Cache (fa38be4f8) - Bug 1145445 - Add a test for CacheStorage; (3512d19fc) - Bug 1145792 - Add a test for the Cache.keys method; (ceae47df5) - Bug 1110814 P1 Implement Cache IPC actor for streaming data from child to parent. (a72a00cd2) - Bug 1110814 P0 Fully initialize Response before resolve Fetch promise. (443df9f44) - Bug 1110814 follow-up: Fix a typo in order to fix the test failures (c89dce5f6) - Bug 1110814 followup: Add missing 'override' annotations to new methods in CacheParent. (3b01c389d) (a0e1e5739) - import change from rmottola/Arctic-Fox: - Bug 1110487 P2 Implement the nsIOfflineStorage interface in Cache. (e61a6d548) - Bug 1110487 P3 Cache should ensure Actions are finished before completing. (0278071c5) - Bug 1110487 P4 Allow Cache Action objects to be canceled more than once. (8734ce14e) - Bug 1149987 - Part 1: Make it possible to send an ErrorResult that doesn't encode a JS exception through the IPDL layer (f8c8abf60) - Bug 1149987 - Part 7: Send the full ErrorResult in the AddAllResponse IPC message; r=bkelly (0201b05e7) - Bug 1145321 - Disconnect the CacheStorage object from its actor when it gets cycle collected; (78aac7cb5) (7f40159c3) - import change from rmottola/Arctic-Fox: - Bug 1146557 P1 Fix CacheStorage and Cache to QI to nsISupports correctly. r=ehsan (b56ba80cd) - Bug 1146557 P2 Flip dom.caches.enabled to true on non-release builds. (b1ac38779) - Bug 1126014 - DomainPolicy support for e10s. r=mrbkap (484fa7f8d) - Bug 1092102 - Implement worker debugger runnables; (cfb3cb53d) - Bug 1092102 - Implement WorkerDebugger.initialize; (24f467b14) - Bug 1092102 - Implement WorkerDebugger.postMessage; (ad69a161d) - Bug 1092102 - Implement WorkerDebuggerGlobalScope.reportError; (f937913f2) - Bug 1092102 - Implement WorkerDebuggerGlobalScope.enterEventLoop; (d1d0ad392) - Bug 1092102 - Implement WorkerDebuggerGlobalScope.setImmediate (a22de0f0d) - Bug 1092102 - Implement WorkerDebuggerGlobalScope.createSandbox (d281de130) - Bug 1092102 followup: Add missing 'override' annotation on DebuggerImmediateRunnable::IsDebuggerRunnable(). (b4d053cfe) - Bug 1092102, followup 2: Add missing 'override' annotation to WorkerDebuggerSandboxPrivate::GetGlobalJSObject() (and 'virtual', for consistency). (72c9f3c84) - Bug 1092102 - Rename Suspend/Resume to Freeze/Thaw; (a7f2b5c11) - Bug 1092102 - Implement WorkerDebugger.isFrozen; (805ba0e9e) (253db3c3f)

that's inaccurate since esr45 branch is not Goanna-based.