NotHereToPlayGames

You should be seeing this "behavior" in Chrome, in Firefox, and in Edge. Safari is the only browser that disables it by default. I think what you guys are seeing is QUIC - https://en.wikipedia.org/wiki/QUIC

All Chrome-based browsers do that, not sure since when, part of "Chromecast". All Firefox-based browsers do that since v36 but I think this is disabled via browser.casting.enabled=false, unsure.

Not sweeping under the rug. I believe I requested the file in question to be scanned by TWENTY anti-virus programs and that if all TWENTY flagged it, then we have a problem. But only one and my sky isn't falling. I used to use a "portable wrapper" called JauntePE, unsure if MSFN folks are familiar with it, almost everything flagged it as a "suspicious" because it "hooks" onto .exe files. Same goes for several systray utilities I've used over the years to minimize programs to the systray instead of to the task bar.

I get 369/15 in 12 M. But my 12 r 8 tops it for me ==

We really don't need the anti-Russian rhetoric, folks. This is an international community. Yes, Russia is in the "Top 10" of hackers around the globe - so is China, so is the USA, so is Turkey, so is Poland, so is Brazil, so is India, so is Germany, blah blah blah...

Page 1? Or Page 55? Both load equally fast for me in 360Chrome v12 (NoScript 11.2.3 enabled) and in Mypal 27.9.4 (NoScript 5.1.9 disabled, render-lag if enabled). If you are using NoScript then that can cause some very serious render-lags in FF-based browsers here at MSFN et alia. But I seem to recall that "newer" NoScript extensions will cause the same render-lag in Chrome-based browsers here at MSFN et alia.

I personally like -- Kraken 1.1 -- https://mozilla.github.io/krakenbenchmark.mozilla.org/index.html SunSpider 1.0.2 -- https://webkit.org/perf/sunspider/sunspider.html Speedometer 2.0 -- https://browserbench.org/Speedometer2.0/ (there is also a Speedometer 1.0 but while the resulting score may be different, the actual "order" of results in comparing several browsers is always the same) BrowserAudit -- https://browseraudit.com/ Basemark Web 3.0 -- https://web.basemark.com/ PassMark AppTimer -- https://www.passmark.com/products/apptimer/

No worries. I like "test" and "benchmark" sites but in the end it is usability that trumps test/benchmark "results". There are some "benchmarks" out there that when you see the "results" you simply have to roll on the floor in laughter. A FF-based browser which is quick and snappy and renders all 500 top-500 sites with ease will score 20,000 but an equally quick and snappy Chrome-based browser which again renders all 500 top-500 sites with ease will score 40,000 on the same exact OS and hardware. "Yeah, right!"...

I'm not sure what the objective here is. Track down "test" sites whose sole purpose is to "crash" a web browser? These will always exist "in theory" and really not worth the effort to prevent (in my view). If a top-500 web site like YouTube, Google, Wikipedia, Facebook, et cetera causes crashes, then that is something worth looking into. But some "test" site whose sole existence is to create hypotheticals that simply do not exist "in the real world" ???

It's like a car alarm. You hear them ALL THE TIME. But the car is NEVER being broken into. Just some fat-finger owner that hit the wrong button on the keyless entry or some dog p!ssed on the tire and the sensitivity was way too high. Scan it with twenty different "tools" and if all twenty flagged, then I'd be concerned.

Does the original Chinese v13.0.2206 also crash for you against html5test? I still wouldn't use html5test as "the" tell-tale.

Yep. All of my extensions are over a year or so old. Most are NOT the "latest and greatest" because the OLDER versions are lighter and more efficient.

Don't get me wrong, I'm very curious on the newer v13.1 and v13.5 because of the random crashes in v13.0. I've been using v12 as my default because of those random crashes. But it still seems odd that I ran v13.0 for close to six months or so before it started doing those random crashes - it was ROCK SOLID for very close to six months, NEVER a single solitary crash. Almost like a "time bomb" was embedded into the code that hasn't been found yet. We axed all of the telemetry we could find - but "did we?" Is there some sort of "time bomb" that 'collects' data for six months or so and these random crashes are because it's now trying to "do" something with that 'collection'? But CAN'T because we axed the code. Just seems very strange to me that I was running v13 for that long without a single solitary crash and now it crashes daily. ~ "Things that make you go hmmm"...

Yeah, I guess basically ALL browsers are "beta". Weekly updates. Nightly branches. Impossible to keep up. False sense of security by end-users thinking the only way to be "secure" is to update their software three or four times PER DAY. Googled for curiosity, found three articles in less than 15 seconds that "recommend" you set your anti-virus software to check for updates every 30 minutes - b#llcr@p, I don't even install anti-virus software! Oh well...

And there really is HOURS upon HOURS of work required in order to build these rebuilds. I cannot spend HOURS upon HOURS for a BETA then turn around and do it again for a "better BETA" a month from now, then again for another "better BETA" two months from now. As mentioned earlier, once v13.1.x or v13.5.x makes it out of "beta" then I'll likely revisit - WAAYYY too many hours involved to construct beta after beta after beta.

Address positions do not line up, can't just copy files between different build numbers.

Documentary Letter of Credit ??? Data Link Control ??? Developmental Learning Center ??? Distributed Leader Course ??? Disability Law Center ??? Dominion Lending Centre ??? Democratic Leadership Council ??? Digital Loop Carrier ??? Dual-Layer Capacitor ??? Date of Last Contact ??? Diamond-Like Carbon ??? Diamond Like Coating ??? Dioxin-Like Compound ??? Diagnostic Link Connector ??? Oh! Downloadable Content! But I had to get this far into an acronym list to find out what in Hades this "joke" was all about.

Same here. MSFN is one of those random crashes - start to reply to a topic, walk away from the computer for a minute or two, return and browser has crashed, seems to only happen when a reply has been started. I've not been able to track down the actual cause - but this happens in XP only and happens in all three of v13's -- in my v13 [2206], in Humming Owl's v13 [2250], and in Dixel's v13 [1106].

I cannot replicate any crashes on html5test but nor would a crash there prevent me from using the browser elsewhere as far as that is concerned.

Upon some trial runs on v13.1.x and v13.5.x, I will be keeping my v13 rebuild at build 2206. There has been no "engine" upgrades to any of the 'newer' releases (they all use the same exact Chromium Engine used by build 2206). Just a TON of "bloatware" and useless features not needed to just "browse". Crashes on html5test do not concern me - by the time we wittled away all of the "bloatware" cr@p then html5test would likely continue to crash, no real loss in my view. Once v13.1.x or v13.5.x makes it out of "beta" then I'll likely revisit - but for now, there is no "value-add" beyond 2206 from what I can see, just a bunch of added JUNK (even an added SERVICE that continues to run even after you close the browser!).

<blocked iframe> I'll look into an updated v13.1.4010.0 but it will likely be a couple of weeks.

I'll look into it, might be a couple of weeks.

I thought that most browsers already included this without any need for an extension. In Chrome-based, you do this by holding Ctrl-Shift down then clicking on the link - the link then opens in a new tab and that new tab is activated. I know this throws the keyboard into the mix and a context menu would be mouse-only, but does Ctrl-Shift (or similar) do the same thing for FF-based? FF used to have a browser.tabs.loadInBackground preference setting (set to false for your desired result), unsure if this is still usable in St52. edit - oops, you did say "without reaching for the keyboard"... hopefully setting browser.tabs.loadInBackground to false will work for you...