NotHereToPlayGames

No, not really. I uploaded 13.5.2022 with the swiftshader .dll's. I uploaded 13.5.1030 without the swiftshader .dll's. The swiftshader .dll's SHOULD BE INCLUDED !!! There was a FALSEHOOD spread about the forum that swiftshader is not supported by XP and only applies to Vulkan graphics cards or something like that. But this is NOT 100% TRUE. The BACKPORTING by the 360Chrome developers REQUIRE the swiftshader .dll's otherwise certain GPU processes WILL CRASH. This "requirement" will plague some systems more than others (ie, very first launch after a system restart). It is true that Vulkan is "disabled", but the swiftshader .dll's do "more" than that, they are required in order for 360Chrome to function 100%. You can witness a GPU crash error on the chrome://gpu page, at the very bottom. Not all GPU crashes will result in 360Chrome crashing, but I do suggest KEEPING the swiftshader .dll's. On my system, I only keep the sub-folder .dll's and not the root folder .dll's. But there may be some systems that work the other way around. At any rate, for a apples-to-apples comparison, you have to put the swiftshader folder back into your 13.5.1030 version.

I have been investigating that very thing. My thread on that investigation is here -- https://msfn.org/board/topic/184322-narrowing-down-my-default-browser-for-my-win10-setups/

I have a "SmartWhois" entry in my click-to-access Proxomitron Menu that gives me that info. But I only access it "on demand" as opposed to performing "real-time". I personally avoid any extension that has to fetch "updates" and I'm not fond of "real-time" data lookups that make their own internet connections whenever they feel like it. I like the idea of a LOCAL database that I myself would have to update in the event that an "unknown" icon shows up instead of an actual flag.

True. I was given faulty intel. I should have known better and resorted to "trust but verify".

Thanks, I suspected that would fix it for you. Even though "swiftshader" isn't 'supported' by XP and is 'supposed' to only apply to Vulkan API, the REALITY is that the upstream developers are using these .dll's for OTHER purposes and KEEPING them makes 360Chrome MUCH more STABLE for certain setups. Those that don't need them, fine, they can delete them. But some of us DO need them.

True. Regarding the chrome://gpu page, take note of the "Diagnostics" section. Compare/contrast that section when your 360Chrome includes the SwiftShader .dll's versus excludes the SwiftShader .dll's (excluding causes crashes on first launch each and every system restart for me).

I'm more interested in finding a precise and repeatable process in getting fonts to disappear in v13.5.

Agreed. Same observations here.

Could perhaps try this one also -- chrome://flags/#disable-accelerated-2d-canvas I cannot test here at work but I seem to recall I was using this when I was on v11 but before I tracked my disappearing fonts to using too new of a version for Stylus. On my setup, I used to get disappearing fonts daily but I've never had them in well over six months after dropping to an older version of Stylus.

Here, extract and make sure the folder structure matches what I showed earlier. If it works for you (as it does for me!), then others will learn from this also. https://www.dropbox.com/s/o07tky04j7m1fka/swiftshader.zip?dl=1

It's not that cut-and-dried. 360Chrome v13.5 (and any 13.0 newer than 2206) CRASHES on my XP without the swiftshader .dll's -- it's one of the biggest reasons I had zero interest in anything beyond 13.0 build 2206 for the longest time. I do not have any crashes with the swiftshader .dll's included. Q. E. D. -- As our friend AstroSkipper would say

I probably didn't include them in the upload because it seemed that nobody else required them. I'll upload a new build later this week (I lost track of all the changes, gstatic and download translation comes to mind).

If Kee is working, then ignore the console error . If Kee is NOT working, then that is a question to post on a Kee-user forum or perhaps a new thread here at MSFN to attract other Kee users (they will likely not see the question posted in a 360Chrome thread).

I saw three or four articles claiming that Google themselves suggest users to use a different browser instead of using their own browser with the --no-sandbox switch. BUT this doesn't really say much, in my opinion. Malware/Virus advocates basically make the same claim about running a computer without anti-malware/anti-virus. Yet I've not ran either, not even "on-demand" scans, in over 15+ years - and I have never been hit with malware or virus! It's about knowing what to click and what not to click, what web sites to trust and what web sites not to trust, when to allow javascript, when to block javascript, et cetera. I myself would use this switch IF my fonts disappeared as often as it seems to for others AND if the switch resulted in lower RAM (which was not the case when I measured on XP x64, but I only took one comparison instead of an average of several). I myself would NOT use the "Spectre mitigation" switch IF it did not result in Cloudflare capcha issues (because that switch does lower RAM).

Mine used to also. For me, the fix was to KEEP the two swiftshader folder .dll files. But do note that the same two .dll files (by name, not by version) used to exist in the root folder also - perhaps some computers need the root folder .dll files and other computers need the swiftshader .dll files and still other computers need none of them.

I can get fonts to disappear in 360Chrome v11 each and every time and it only takes 15 seconds. 1) open this web site in 360Chrome v11 -- https://forum.eclectic4un.me/ 2) minimize 360Chrome v11 3) launch Serpent v52 4) click Ctrl-T to open a new tab 5) close newly opened tab 6) exit Serpent 52 (note, I didn't do any browsing, my St52 opens an about:blank tab and my new tab is also an about:blank tab) 7) restore 360Chrome v11 window that was previously minimized -- the username on posts will no longer be visible Works 100% of the time! Setting the --no-sandbox switch does indeed prevent fonts from disappearing. However - I can not get fonts to disappear in 360Chrome v13.5 build 1030 or in 360Chrome v13.5 build 2022, even with 360Chrome minimized for half an hour while browsing with St52, St55, and NM28 during that half an hour.

My dad passed away about a year ago at the age of 82 - all COPD/asthma related. He was advised to *NOT* get any of the Covid shots. He ended up getting Covid *SIX TIMES* - none of them hospitalized him, none even constrained him to a bed, none even gave him digestive distress. edit - OT, of course...

On my XP x64, the --no-sandbox option seems to require an additional 13 MB of RAM.

Bummer. How often would you say the disappearing fonts occur (I have witnessed disappearing fonts but I haven't witnessed for well over two months)? Once every hour without --no-sandbox? Opposed to once every three weeks with --no-sandbox?

Do you happen to have a consistent repeatable scenario that causes the disappearing fonts? Something like it "always" happens in Site F each and every time you have Sites A, B, C, D, E, F, G, H, and I open?

Depending on your definition of "manager" -- I "manage" all of my passwords by using an "auto-fill" extension (I disable 360Chrome's Personal Data settings for saving passwords and autofill). I use Autofill version 10.3.4 -- https://www.crx4chrome.com/crx/303031/