D.Draker Posted March 29 Posted March 29 (edited) @ED_Sln, as promised, I'm back with my opinion about the Unghouled 134, overall, it's a good browser for someone with 16GB+ of RAM, at least highly overclocked DDR3 1866. It's fast and snappy, but RAM usage is heavy, despite being 32bit. Here I post my screens with and without the browser opened. Thank you for the find, again! Memory hog! Edited March 29 by D.Draker rough day consequential typos 2
D.Draker Posted March 29 Posted March 29 Oh, and I haven't witnessed hostile connections to anywhere,
D.Draker Posted March 29 Posted March 29 *The tests were intentionally done on an old "torture" PC where I perform tests. It's an old machine with 8GB or RAM and an OC Core Quad Q9650. One pleasant thing to admit. it has NO stupid nag screen about Vista anymore!
D.Draker Posted March 29 Posted March 29 Not actually suitable for streaming to a Home Theatre due to the lack of Dolby and H265. No biggie for the most here, I guess. 4
Saxon Posted March 29 Posted March 29 @D.Draker, would YOU suggest to try this browser over Supermium? I've been looking for 32bit for ages!!! 3
D.Draker Posted March 29 Posted March 29 10 hours ago, Saxon said: @D.Draker, would YOU suggest to try this browser over Supermium? I've been looking for 32bit for ages!!! ME? Lol. Over Supermium? Of course! Any second! Supermium is buggy (to put it very mildly and politely). With this one, I was able to use my old Ungoogled profile from over two years ago, without the icons and tab distortions many, including @Jody Thornton were having. Over Supermium? Especially after this. https://msfn.org/board/topic/185045-supermium/page/123/#findComment-1279153 4
D.Draker Posted March 29 Posted March 29 Back up your profile first!!! Copy it to the new browser. Then start the browser with these. --disable-machine-id --disable-encryption-win Voila! Now always start using those flags, only one time without them would be enough to get the profile lost!! 3
D.Draker Posted March 29 Posted March 29 11 hours ago, Saxon said: @D.Draker, would YOU suggest to try this browser over Supermium? I've been looking for 32bit for ages!!! Oh, and the UI is neat and clean, unlike in Supermium. NO over-brightness issues or blurry, over-contrast texts, like Supermium/Thorium has. 2
ED_Sln Posted March 29 Author Posted March 29 5 hours ago, D.Draker said: It's fast and snappy, but RAM usage is heavy, despite being 32bit. Maybe it's the same problem as it was with Chrome-like browsers in WinXP, when they consumed a lot of memory due to installed C++ 2015-2019. Try unzipping those dlls into the browser folder, if the memory consumption drops, then that's it. corrected_api_sets.zip
Klemper Posted March 30 Posted March 30 On 3/29/2025 at 6:49 AM, ED_Sln said: due to installed C++ 2015-2019 D.Draker doesn't have those installed, I know for sure because I closely follow this man and read his posts.
D.Draker Posted March 31 Posted March 31 On 3/29/2025 at 8:58 PM, Klemper said: D.Draker doesn't have those installed, I know for sure because I closely follow this man and read his posts. Right! I have no need of those, I keep my system clean. @ED_Sln, nothing changed, but thanks!
D.Draker Posted March 31 Posted March 31 I forgot to tell, manifest v2 extensions work flawlessly in this browser v.134.
D.Draker Posted March 31 Posted March 31 @ED_Sln, client hints are not disabled in this "ungoogled" fork. Either the original Ungoogled developer lied, which is not rare, as we saw earlier, or this fork is not completely ungoogled, but I'd like to to the bottom of this, thanks. https://github.com/ungoogled-software/ungoogled-chromium/issues/2887
ED_Sln Posted March 31 Author Posted March 31 8 hours ago, D.Draker said: Either the original Ungoogled developer lied, which is not rare, as we saw earlier, or this fork is not completely ungoogled, but I'd like to to the bottom of this, thanks. Looks like that flag just got changed, so now it's --enable-features=RemoveClientHints In chrome://flags it's called #remove-client-hints
D.Draker Posted March 31 Posted March 31 13 hours ago, ED_Sln said: Looks like that flag just got changed, so now it's --enable-features=RemoveClientHints In chrome://flags it's called #remove-client-hints Thanks, it doesn't disable the API, I already tried it before. This non-working flag is a gift from @VistaLover. From the times he was trying to make Supermium somewhat usable. Supermium BROKEN "ClientHints API Removal" implementation #838 Source: https://github.com/win32ss/supermium/issues/838
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now