NotHereToPlayGames

ps - why do you report DcBrowser findings in this thread? DcBrowser is a Humming Owl release and I've seen too much telemetry not yet removed so I no longer even have access to it. Shouldn't those findings be posted in Humming Owl's thread?

Have you tried using about:blank as the empty tab instead of using a chrome://newtab/ (which is the URL for the default "new tab"). Other than that, the difference between 19,904 and 16,940 is tiny, relatively speaking. I have not loaded "Dark Empty New Tab" for my own compare-contrast.

FYI - I would not refer to your builds as Ungoogled because the Chrome Web Store feature needs broken to be truly in-step with standard Ungoogled Chromium.

I think the Preference file's accept_languages file also needs changed. There are portions that seem to go by language pak file name. But I seem to see just as many portions that go by accept_languages. Not sure how these are passed on to the visited website. It just seems that both are required for best language compatibility. "It all looks Greek to me."

Please don't make "demands". Please make "requests" instead. Clearly a "language barrier". Not worth "arguing". Have a great day!

If you want WebGL, that's on you. It is a security risk and unneeded. I have removed it for a reason and I will not be adding it back in. Again, if you want WebGL, that's on you.

My neighbor 1/4 mile down the road just called. She wanted to know why I was laughing so loud and that she heard me all the way over at her house.

I have already answered this question. You have to enable WebGL and copy switftshader folder and the .dll mentioned when I answered this question the first time. You put a "like" on it, so I know you saw it.

Seriously - uncalled for !!!

Have you ever looked up the informal definition of "high maintenance"? I wouldn't add an extension just to change an empty New Tab. You can create your own New Tab and be creative as you want with it (I personally don't use "bookmarks" and use my own New Tab with all of my favorite links). Place this file in the same folder that contains "chrome.dll" (and test by disabling "Dark Empty New Tab") -- https://www.dropbox.com/s/5yy90s71jcnu5qw/newtab.zip It's nothing more than an .html file inside a .zip and you can be as creative as you want with it, limited only by your own imagination. Uncalled for !!! What you define as a "problem" does not qualify for what others define as a "problem". Some of your "problems" really do require you to start learning how to do some of these modifications yourself instead of thinking us "developers" are here at your becking call.

Info for Humming Owl (only tested v11) -- Unsure if this is all that the OP requires or not and I cannot test fully as I cannot get the Asian Language Pack to install in an XP VM. If I change "accept_languages": "en-US,en" to "accept_languages": "zh-ch,zh,en-US,en" in the Preferences file (the ,zh, part is an outright guess) [and unsure where a hard-coded equivalant is located], then I get this at https://passer-by.com/browser/ --

Drop the quality to a lower level. Nobody really "needs" 1080p 100% of the time. Sometimes we bring upon our own problems via unrealistic expectations. That's my only guess as I have no playback issues in v11, even at 1080p.

Getting Old !!!... ... ...

<double post>

To restore those two maps, you will need to make your browser "less secure". Edit the loader .ini file and remove these two entires ::: --disable-webgl --js-flags=--noexpose_wasm (you will need webgl for sure, unsure if the latter entry needs removed or not) Then copy the "swiftshader" folder and the libGLESv2.dll from any of Humming Owl's releases into the equivalent folder structure in my release. But do this knowing that these were removed for the sake of added security. "swiftshader" is not limited to Vulkan GPUs, though it may have been when first introduced. It is required for those "3D" maps. I personally advise against enabling webgl (required for swiftshader) just for the sake of a weather forecast (weather web sites are a dime a dozen) - but totally your call, it is your computer

There is a "player" involved for those "maps" (you can see it in Dev Tools).

That made it worse! I went from 60% to 80% lockup rate to 100% lockup rate. Before I would at least get the address bar and tab bar, with this suggestion I don't even get that! I do not use fullscreen mode either (but I don't really see it as for "security reasons", kind of sounds like a Red Herring but I've not researched it).

Didn't work. Took only two reboots and first-launch-after-reboot locked up on second reboot. The lockup isn't "every" first-launch-after-reboot, it's closer to right around 60% to 80% of first-run-after-launch - a majority and an outright nuisance.

That's personally one of my bigger reasons for 360Chrome. I have x64 7 and x64 10 on two laptops -- but using "older" software is much more efficient and less resource-hungry. I don't "need" 360Chrome for 7 or 10, "official" versions, be it Mozilla-based or Chromium-based, already run on those OSes - but at huge cost to resources.

Too hillarious. Nice to start the day off with a good chuckle.

Bingo!

AGREED !!! HEAVILY AGREED !!! My "workhorse" is an i7-4770 at 3.4 GHz with 16 GB RAM. Purchased late 2014 with 8 GB RAM for just shy of $700. I've since upgraded to 16 GB RAM. It came pre-loaded with Win 7 x64 but "updated itself" within 6 months or so to Win 10 x64. I was pretty much immediately "enraged" with Win 10 and how dare my computer "upgrade itself" !!! I should have known better, I disabled all of that auto-update crap in XP but forgot to (or just never got around to) disabling in 7 and here I was in 10 and hated it! I was going back to 7 no matter what but took time to contrast real-world same-hardware performance metrics between XP and 7 and the winner, bar none, was XP. This "workhorse" has been on XP every since (we can all "agree to disagree" on why MILLIONS of us worldwide have come to the same conclusions and REMAIN on XP). Though I should add here that I have since tweaked my 7's and 10's but haven't repeated the contrast-and-compare same-hardware performance metrics to XP. My main point is this - me buying the i7-4770 did not make my Core 2 Duo's and my Core 2 Quad's "useless" -- why would I throw them away when they are EXTREMELY usefull as-is? But that also doesn't mean they are "worth" throwing money at (and I do take issue with forum members 'telling me' to go buy RAM for my Core 2 Duo's and my Core 2 Quad's!). I own four "classic" cars. A '55, a '61, a '90, and a '91. Cars and computers are "hobbies". I will "throw money" at a '55 or '61 without hesitation, there will be hesitation at how much money is thrown at a '90 or '91. But if my "daily driver" starts to require "money thrown at it', you have to wheigh the pros and cons very heavily -- if that "daily driver" requires money thrown at it "left and right", then HELLO, trade it in for something more reliable! Again, I take very serious issue with forum members 'telling me' to go buy RAM for my Core 2 Duo's and my Core 2 Quad's -- not going to happen! They are VERY useful to me as-is and I will cut bait with them as soon as they are no longer useful to me. But I will not "throw money at them"!

Even without the first-launch-after-reboot lockup issue, I cannot even "force" myself to use v13.5. It's an outrageously gigantic RAM hog and I don't use any of my computers to "just browse". They'll all have several programs open and have several browser windows each with several tabs. I'm reminded of several weeks/months ago where it seems like the ONLY "endurance test" that ANYBODY cared about for these browser was "How many YouTube tabs can I open before it crashes?" You may recall that it made ZERO sense to me at the time, why would ANYBODY want to have twenty YouTube tabs open? I can only watch ONE. I can only listen to ONE. Point is, we all use our computers for different things and we all have different needs. v13.5 is not the wave of the future for 360Chrome, it just isn't. We will just have to "agree to disagree". My focus remains on "low-end" "older" hardware. We simply should not need 3 GB RAM or more just to launch a web browser. Apologies if I came across as in a "bad mood" earlier. But I'll have to take this stand that v13.5 is not the wave of the future for 360Chrome. I do firmly believe that. I am interested in keeping all of these as up-to-date as is reasonable. But I see no advantage to dropping v11 or v12 just because v13.5 is "newest". In other news, I know that Humming Owl likes to keep his releases at the "latest" (whereas I try to benchmark different builds and cherry-pick among them) -- v13 build 2250 has been updated to build 2256 as far as the original Chinese goes.

Cool !!! My v13.5 seems to only have that first-launch-after-reboot lockup nuance on MULTI-MONITOR computers. Not sure why that would cause any issues but that's the best I got so far. Any computer with only ONE monitor is totally and absolutely USELESS to me

The irony in the post by NoelC -- he observed 8.1 as being SLOWER than 8 which in turn was observed as SLOWER than 7. But what did he do with those observations? He upgraded from 7, skipped 8, and went straight to 8.1 -- despite his observations with it being the slowest of the three. So I think the bigger question is this -- why did he upgrade, why didn't he just stay on 7? Especially considering the post was December 2013 and Win7 still had extended supported all the way through January 2020 (and I've heard rumors that some have found support channels through 2024, I've not research that as of yet).