NotHereToPlayGames
Content Type
Profiles
Forums
Events
Everything posted by NotHereToPlayGames
-
Relaunch DcB on the 2 GB VM and RAM/process drops to around 30 MB.
-
Here's the same three browsers but with VM RAM increased from 1 GB to 2 GB. Note that v11 stays at four processes while DcB and Ungoogled v77 both increased in the number of processes despite being the same four tabs. Also note that a DcB process on a 1 GB VM is roughly 30 MB but a DcB process on a 2 GB VM is roughly 110 MB !!! This seems to suggest that the rebase address has to be somehow based on the system's overall available RAM.
-
Multi-processor web browser RAM usage is not "linear". The browser decides how many processes to run based on number of open tabs and available RAM. Run the same exact browser on a computer with 1 GB RAM, 2 GB RAM, and 4 GB RAM and you will get different RAM consumption. Here is my 360Chrome v11 rebuild 8 on XP with 1 GB RAM, Humming Owl's DcBrowser on XP with 1 GB RAM, and Ungoogled Chromium v77 on Win7 with 1 GB RAM.
-
Add the below (after editing) startup command to your shortcut or in the loader.ini file if you use the loader. --user-data-dir=<drive>:\<folder_path> You should add quotes after the = if the drive or folder path has any spaces. --user-data-dir="<ram disk drive>:\<folder sub directory>"
-
Agreed.
-
ps - define "crash". There was a "360 sync login" that was intentionally disabled that was triggered whenever creating the FIRST bookmark. By NOT creating that FIRST bookmark but clicking that star three times, maybe that has retriggered the "360 sync login". This will be INVISIBLE because the GUI items were removed when the "trigger" was set as "already-triggered" in the default PREFERENCES &/or WEB DATA files (which if you replaced then that too could lead to this "360 sync login" being triggered). At any rate, this may NOT be an actual "crash". HIT THE ESCAPE KEY on the keyboard when this happens and see if the "crash" is un-crashed. The ESC key "closes" the '360 sync login' trigger that would be "invisible".
-
Thanks. I did not know (or misunderstood) that this was with ZERO BOOKMARKS.
-
This would be telemetry by Fifth Third Bank and not by 360Chrome. Have you tried in any other browser, both Chrome-based and Mozilla-based?
-
I still cannot replicate. Clicked the left star TWENTY TIMES with an empty tab, TWENTY TIMES with this one MSFN tab. Clicked the address bar star TWENTY TIMES with an empty tab, TWENTY TIMES with this one MSFN tab. I cannot replicate.
-
Do you get this dialog box on the FIRST CLICK ?
-
Can not replicate in XP. I do not / can not run on Vista.
-
Plus, that screencap does not have "my XP blue" skin, so whatever you did to remove the "XP blue" could be your problem. I see the "XP blue" under your Win2k-basic-gray.
-
That and I can not replicate this claimed behavior here.
-
Don't click three times! Problem solved. Yeah, it's kind of "that easy".
-
Agreed. Plus, "se" and "ee" are two different branches. 360Chrome has basically had three different v86 engines - 86.0.4195.1 86.0.4240.112 86.0.4240.198 As far as a true scientific quantitative approach goes - The .1 engines were the FASTEST. The .112 engines saw a very slight performance degradation. The .198 engines (everything newer than v13.0 build 2206 and all of the v13.5 builds) saw another very slight performance degradation.
-
Same here!
-
It's only enabled because you were using in an unintended fashion (that I do not recall you admitting to prior to today). So you have to blame yourself for that. You chose to use by your own rules, so no, of course it didn't work as it was intended. The topic of your WebGL being enabled or disabled can hereby be considered CLOSED. Further discussions only confuse new visitors. Bottom line - you used it in your own way, so you didn't get the results you were supposed to get because of using it in your own way. Q.E.D.
-
If it's any consolation - A year or two ago when I started these public-share rebuilds, I opted to disable WebGL based on "security vulnerabilities" associated with WebGL. Most of those "security" reports with WebGL are dated circa 2011. Most of the "vulnerabilities" were later addressed by way of "same-origin policy" restrictions coded into the web browser. How "insecure" is a web browser in 2023 because of WebGL coupled with same-origin policy restrictions that did not exist in 2011 when these "security vulnerabilities" were first raised? Should I be "paranoid" about WebGL exposing OpenGL to JavaScript when I only allow specific whitelisted javascript? I have currently opted to enable WebGL and maybe, just MAYBE, I was a bit too "paranoid" to disable it in the first place.
-
If you do not use the loader.exe, then the loader.ini does NOTHING. If you are trying to DISABLE WebGL, then you either must use the loader.exe or the --disable-webgl startup command. You are not using EITHER and then you wonder why WebGL is still enabled ??? ??? ???
-
Before I can assist any further, I need all of the following in ONE screencap - 1) Task Manager showing "360Loader.exe" 2) File Manager window showing the 360ChromePortable_13.5.1030_r8_regular_webgl-disabled_translate-enabled_win-xp-skin contents of "360Loader.exe" and "360Loader.ini" 3) Notepad showing "--disable-webgl" 4) ONE tab open and ONE tab ONLY showing top section of "chrome://gpu"