NotHereToPlayGames

Did you also try "ReBase.exe"? Or did you only try "libase.exe"?

Correct, I've seen it for a few months. But the problem is there is never really a "final" v13.5. I kinda don't plan on updating build 2036 only for upstream to release another build weeks later. Not a fan of dog chasing its own tail with all of these "updates". It would be one thing if we could isolate actual WEB SITES that work in build 2036 but that do not work in build 2022 or build 1030.

UN-REBASED first-launch-after-hibernate on my oldest XP x86 -- 13.5 build 1030 versus 13.5 build 2022 -

Agreed. And I just double-checked, I have been running site isolation for the last couple of weeks. "Spectre" mitigation is ZERO priority as far as my browsing needs. But now with Cloudflare not liking it, I did switch it back to default on my setup. It is a "balance", I'd rather consume more RAM but be 100% functional. Not "everything" boils down to RAM in my book. edit - I also switch to UN-REBASED build 1030 as my default. But it seems a splitting-of-hairs between it and 2022.

Yeah, my bad, I was experimenting with some flags and didn't intend to upload with that flag set. That flag does decrease the number of processes and thereby cuts down on RAM but I don't run that flag with my default config.

Yeah, I was kind of afraid of that. Rebase address will be heavily dependent on the end-user's system.

I actually prefer the NON-REBASED build 2022. Fast-as-possible launch coming out of hibernate trumps the extra RAM for my preference.

lol. You preferred 1030 over 2022 so that was one of the driving factors to release a 1030.

Yeah, build 2022 is "newer" than build 1030. Build 1030 was more for the @AstroSkipper types.

13.5.1030 does not pass. But 13.5.2022 does pass.

Correct, "normal" in-browser means will not delete the Google cookie. I for one cannot blindly trust a Google cookie on a Google web browser that has a "delete cookies" user-preference but ignores the user-preference and applies its own hidden rules toward that Google cookie. I use Google for search and for translate (but not the built-in context menu translate). Everything web-based Google works without allowing the telemetry from the Chrome Web Store setting a Google cookie. Having to install extensions through other methods is a small price to pay.

No.

There is no answer to that! Browser choice has always always ALWAYS been about "personal perference". What works for me, will not work for you. What works for you, will not work for me.

I stopped upgrading mine at v4.17.4808.

I would not use either on Vista. I would use (and do use) v94 forks for anything I run with Vista or higher. I have no need for anything higher than v94. And there is no such thing as "future proof" - we can only find what works for us "today" and we have to decide for ourselves if we want to be a dog chasing its tail with constant updates that gain us nothing or if we are content with running "old" and not having to deal with the hassle and nuisance of constantly upgrading.

Correct. The downloads from the first post already contain rebased chrome.dll.

That seems to be pretty common when you have .css/.js coming in from SEVERAL web sites and "one" of those SEVERAL gets blocked.

Tutorial posted in Post #2 -- https://msfn.org/board/topic/184266-arcticfoxienotheretoplaygames-360chrome-v135-build-1030/?do=findComment&comment=1233828

Absolutely. I'll post a small tutorial in Post #2 of this thread and will report back once I've created it.

Correct. I've "accepted" the trade-off of correctly-allocated RAM over launch time (at least for now!).

For reference. Rebased 13.5 build 2020 versus rebased 13.5 build 1030 versus rebased 13.0 build 2170. Intel Core2 Quad Q6700 @ 2.66 GHz with 3.24 GB available RAM.

You have to have one or the other, you can't have both. Enabling Chrome Web Store to funtion "as intended" also enables a cookie that you can not delete, a cookie that sends telemetry to Google, a cookie that you can not delete, a cookie that talks with each and every web site you ever visit, a cookie that you can not delete, a cookie that tracks your web usage across all browsing sessions, a cookie that you can not delete, a cookie that is even set in Incognito Mode, a cookie that you can not delete. This cookie is constantly sending "data" to Google. You don't have to sell your soul to Google to download extensions. There are better ways. I'm not so privacy-conscious that I wear a tin foil hat, but things like blocking this Google cookie doesn't require any tin foil. But I do cook all of my Christmas cookies on foil because then the cookie pan last a very long time.

lol, too d@mn funny. I have to laugh out loud at some of the "history" here at MSFN.

Cool, that's a relief.