NotHereToPlayGames

I didn't get any error warning, just a crash. It was always when logged in and entering text in the reply box. And it was always very lengthy replies - all lost when the browser crashed. When I was trying to track it down, I would OPEN the reply box but not even type in it. Leave the reply box OPEN and browse in a different window. Sometimes 30 seconds later, sometimes 15 minutes, but MSFN would ALWAYS crash if the reply box was open. I haven't returned to v13 as my default browser on account of random crashes and it happened on versions that I had used for MONTHS unchanged/unmodified without ANY crashes, then all of a sudden the same exact version, brand new profile, would crash left and right. I gave up on v13 and much prefer v12. Even the v13.5 that I've been experimenting with has random lockups only during startup (with or without a profile already in place). No crashes during browsing, just lockups at startup (maybe only 1 in 500 starts, but a lockup is a lockup and I run v12 because it's never had any of the issues that keep popping up with v13). And ONLY on XP.

Cannot replicate. I don't get the qr-code popup. Do you get it on a clean profile? I think I'll just leave the default "Share page", reupload, and call it our official "rebuild_1". Save dark theme for as-time-permits.

I cannot replicate. This could be due to OS-specific font or DPI settings on your computer.

This one might have to stay in the context menu, still digging - it is disabled, it's just still "visible" in the context menu and I've changed it to (disabled feature). This is one of those "added BLOAT" items that didn't exist in ANY of the previous v11, v12, or v13.0 builds.

Download link for v13.5.1030 Beta_2 added to first post. Alpha links removed to free up storage space in Dropbox. Should be 100% functional at this stage - only remaining changes are to remove one minor GUI context menu entry and to create a dark theme.

I see this in the context menu and have placed a "(feature disabled)" placeholder in the menu until I can find where to remove the menu line completely. Kind of a temporary fix for now.

My apologies. I had to clear out my Dropbox to make room for hosting rebuilds and this thread was dead so away they went to free up some storage space.

I was actually toying around with a "Halloween Edition" but time kinda got away from me and it's taking more time than expected. A witch flying to the left for "back", a zombie walking to the right for "forward", a black cat with a swooping tail for "restore", a tombstone for "home", a witch's pot for "bookmarks", a pumpkin for the "menu". Orange text on a dark gray background (which was planned to evolve into green text on a dark gray background for a "Matrix Edition"). It was more for fun as an interim before an official "dark theme" but like I say, time kinda got away from me.

Found this and this will be resolved in Beta_2.

For what it is worth, my version of v13.0 ( this thread ) also crashes here at MSFN. It started crashing here at MSFN roughly two months or so ago, I forgot when exactly but I dropped down to v12 as my default and haven't had any issues since. I am in-process of rebuilding a v13.5 but I have not used it extensively enough to see if it suffers the same crashes that v13.0 suffers. Other users have been testing it and have better stability with v13.5 then they had with v13.0. @Humming Owl - my WinXP is unmodified, my x64 is an unhacked official SP2 and my x86 is an unhacked official SP3 with none of the POS updates (and I always have to laugh that they called them POS). It is tweaked as far as not running any of the useless services and Internet Explorer is disabled with file name trickery, but all of my OS's are unhacked, no kernel patches, no certificate store hacks, et cetera. And my v13.0, your v13.0, Dixel's v13.0, the original Chinese (several builds), and the Russian Repack (several builds) all crash here at MSFN. I've abandoned trying to figure out "why" and just moved to v12 instead. Maybe v13.5 in the future, unsure as of yet.

I'm not really sure what that speed optimization setting is supposed to do.

It really all boils down to USER PREFERENCE. There is no such thing as a "best browser". Operating system plays a role. Available RAM plays a role. Can the same browser be used on six different computers running different operating systems and different RAM and clock spec's all play a role. Browser A will always perform best on web site U, V, and W. Browser B will always perform best on web site X, Y, and Z. Browser C will always have a GUI more intuitive and ergonomic than Browser D. Browser E will always handle RAM better than Browser F. Browser G will have a wider range of available extensions than Browser H. et cetera... It all boils down to USER PREFERENCE, what balance best fits the USER.

If you "hoard tabs" or do what is called "page parking", then you are better off with v11 or v12. Depends on how many tabs you "hoard" or "park" on. I personally do not hoard or park tabs but it is common for me to have a bare minimum of THIRTY tabs open without any issues. But I do not close the browser with all THIRTY still open and expect the browser to "continue where I left off" and spawn a thirty-tab browser session the next time I open the browser.

My v11, v12, and v13 all use roughly the same amount of memory as other public releases for v11, v12, and v13. I've never had any issue with any of the three versions and one of my computers only has 2GB of RAM -- but I admittedly don't use that computer for anything like YouTube.

360Chrome is based off of Chrome/Chromium and they are owned by Google. There is an option to Delete Cookies on every exit and people that delete cookies every exit do so for privacy and security reasons. But Google doesn't want you deleting the Google cookie so they built in a "feature" that when the user wants to delete ALL cookies, the Google cookie WILL NOT DELETE. This allows Google to track the living crap out of you via a cookie that you thought was deleting when you set the setting to delete on every exit but in fact is not being deleted. It is there FOREVER unless you yourself MANUALLY delete it - which you thought you were doing when you set the setting to delete all cookies on exit. This is a blatant embedded "workaround" by Google to keep THEIR cookie but delete everybody elses. The "ungoogled" version breaks this "shenanigan" and when the user sets the setting to delete ALL cookies on exit, the browser will now do exactly what the user told the browser to do - delete ALL cookies on exit.

v11 requires a "hack" in order for the browser to execute on XP x86 SP2. Not an issue with XP x64 SP2 or XP x86 SP3 and higher. v12 and v13 don't require the "hack" as the original Chinese authors created v12 and v13 to already execute on XP x86 SP2.

I did a TON of benchmarks, to be honest. A TON! There are others, but my primary tests are BrowserAudit, Speedometer 1.0, Speedometer 2.0, Basemark Web 3.0, Kraken 1.1, SunSpider 1.0.2, and PassMark AppTimer. If you truly monitor browser performance (including Basilisk, Serpent, Pale Moon, New Moon, Mypal, Sleipnir, Maxthon, you name it), you will find that browser performance PEAKED in 2018 and have yet to return to those performance levels. It's been downhill ever since. So it becomes a balancing act of performance, functionality, and stability. I actually prefer v13 builds 1006, 1032, 1054, 1088, and 1106 all over build 2206 but I had to satisfy both YouTube users and XP x86 SP2 users and build 2206 was the best balance at the time. I don't actually use the "latest and greatest" for v12 either - I base my build on build 1247 despite there being "newer" builds 1322, 1412, 1458, 1476, 1478, 1502, 1567, and 1592 (at my last count). Nor do I use the "latest and greatest" for my v11 - I base my build on build 2031 despite there being "newer" builds 2052, 2140, and 2251 (at my last count).

I personally prefer v11 but I can't use two of my web sites (which have no alternatives as they are work-related) on it and I want an all-or-nothing web browser so I use v12 for everything. I used to have three or four browser (at least!) and I always had to remember which one was better for this, which one one was better for that, et cetera. That got old very fast!

Agreed! Blocking javascript is an absolute MUST. BLOCK by default, only allow on an as-need basis. While this may be "more true" for XP, this equally applies to newer Operating Systems. Blocking javascript is perhaps the BIGGEST security enhancement an end-user can do to lockdown their web browser, old and new.

Oh, and one of the funnest parts of driving a MANUAL? You know those types of people that TAILGATE folks - what does the person in FRONT do to tell them to back off? They tap the brake pedal. In a MANUAL you downshift and the TAILGATER nearly craps their pants, "Holy S#!t, that car is slowing down without a brake light!" As far as rolling backward on a hill, my '61 has this technology -- https://en.wikipedia.org/wiki/Hill-holder It existed in the LATE THIRTIES.

I once had to drive home from University without a clutch cable! So not only did I have to get the car MOVING but I had to drive FOUR HOURS never once coming to a complete stop.

Unless you speek Chinese, I see zero reason anybody would use 360Chrome based on Chromium 95 that requries Windows 7 when Chrome/Chromium 95 in and of itself still supports Windows 7 (at least until January 2022).

Most are actually innocuous within the chrome.dll because so many files are removed. But it's still better safe than sorry and to remove them from the .dll. 360Chrome in its original Chinese form is the most BLOATED of software programs I've ever come across. A "download" sub-directory with 10 .dll files and 2 .exe files for adding zip decompression, download manager, peer-to-peer, and "bug reporting" - all USELESS in order for a web browser to do what it is supposed to do -- which is to browse web sites. Then there are 7 .dll files in the original plugins sub-directory - just added BLOAT and not needed. The original Chinese "application" directory has FORTY NINE files in it (not including sub-directories). For comparison, Beta_1 "application" directory has TWELVE files in it. It really is unreal how much BLOATWARE CRAP is piled in with 360Chrome. Very reliable and stable and very capable browser when axed down to the essentials! All of the BLOAT is especially fun to watch when you've been around this browser for close to a year now. There is something to be said for using v11 over v12 or v12 over v13. Each newer version just gets more and more BLOAT piled in. There is something to be said for using earlier builds for each branch as opposed to the latest-and-greatest for each branch. It really is the added BLOAT that mostly changes from one build to the next. Newer is not always better. Granted, v13.5 seems to be an improvement over v13.0 -- fingers crossed.

My '55 is a "three-on-the-tree" -- manual 3-speed where the shifter is on the steering column. My '61 is a "four-on-the-floor" -- manual 4-speed with the shifter on the floor and that was what they called them in the 60s. My '90 is a 5-speed manual turbo. My '91 is a 5-speed manual. My '07 is a 4-speed manual.