Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 09/23/2024 in all areas

  1. Of course, it is not related to the rebase of DLL files. I didn't claim that either. It is an old, well-known problem that, however, can be curbed, but only in multiprocess mode. In single-process mode, considerably more memory is not released after tabs are closed, at least on my system. Anyway! There is more to be done to free up memory. One measure I already recommended is the periodical memory minimisation which should be done automatically.
    2 points
  2. The file nssdbm3.dll is missing in your sequence compared with the ones in the previous posts. On purpose or by chance? And why do you think the sequence of the DLL file series is of importance? BTW, I wrote: What are your observations when comparing single-process mode with multiprocess mode in terms of rebasing the DLL file series?
    2 points
  3. Try to start the browser from a short named folder, like C:\Chrome.
    2 points
  4. Hi all, after extensive testings, I'm still sticking with the fantastic 348.01 (pleasant colours), but it's not as good as it supposed to be. Unfortunately, I'm experiencing terrible throttling on all drivers from Nvidia site and on all of the suggested above. Looks like finding the original 348.12 is the only solution. Just like it says here. https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/292634/throttling-on-all-drivers-from-site-nvidia-laptop-/
    2 points
  5. Ok, can we count it as your version of those events then? The browser turns on the lights and spins up the disks, then the chirping sounds follows, and all that just because the browsers from that place are simply bored?
    2 points
  6. You're "done" because you have nothing to contradict to the facts scientifically (which is an expected behaviour on a technical forum), nor you can find any reports of the same behaviour in Chrome 115 Official Build.
    2 points
  7. Regarding the UXP browsers, I stopped using full themes or extensions that change the GUI a long time ago to avoid unnecessary CPU load and negative effects. If I notice that an extension is putting a strain on the browser, it is uninstalled immediately.
    1 point
  8. In the case of Mypal 68, however, the effect of rebasing its DLL files is only sustainable in multiprocess mode as the main problem with most browsers is, among other things, the release of memory when tabs are closed. The browser is not inherently prepared to release the amount of memory that a tab requires to load when this tab is closed again. In the course of a browser session, more and more RAM is therefore used that is not actually required but is no longer available to the system and can usually only be released if the browser is closed or restarted by the user. Unfortunately, the effect of rebasing fizzles out very quickly in single-process mode. And even in multiprocess mode, it is necessary to do more than just change the base address of its DLL files to fully enjoy the effect of rebasing in the entire browser session. Especially on systems equipped with a small amount of RAM where every single megabyte counts. In any case, I have managed to configure my installation of Mypal 68 so that the memory occupied by tabs is almost completely released when they are closed again. Of course, without restarting the browser and being a tab hoarder.
    1 point
  9. Start Mypal 68, open Process Hacker, right-click on the mypal.exe file and left-click on its Properties! Select then the Memory tab and check the base address range from 0x60000000 to 0x6f000000! If, for example, no other DLL file has the base address 0x60000000 and behind it is enough free address space for the DLL files to be rebased, then of course you can also start with the base address 0x60000000 for rebasing the DLL file series. For testing purpose only, I have rebased the DLL file series to the base address 0x60000000. As I already assumed, it works in the same way as with the other addresses. Here is a screenshot: I should still mention that I checked the base address range before rebasing. The range from 0x60000000 to 0x66700000 was not occupied by any other DLL file.
    1 point
  10. Counter question. Why does the libase tool automatically select the base address 0x6af00000 for xul.dll, which is exactly in the range from 0x60000000 to 0x6f000000? In any case, this recommendation did not originally come from me, but from an article I found after a research via Google. Here is the decisive section as a quote: This section can be found here: https://www.codeproject.com/Articles/35829/Modify-the-Base-Addresses-for-a-DLL-Files-Series And as you see, @UCyborg also seems to prefer addresses inside this range for his DLL file series: And I have also had good experiences with this base address range for DLL files. Cheers, AstroSkipper
    1 point
  11. In fact, it was uCyborg who first suggested (in Dezember of 2022) rebasing the chrome.dll file in 360Chrome as a measure to curb this browser's hunger for memory and pointed to the tool libase: https://msfn.org/board/topic/184135-arcticfoxienotheretoplaygames-360chrome-v1352022-rebuild-3/?do=findComment&comment=1232976 On my hardware, rebasing the chrome.dll was a complete success and actually resulted in a significant reduction of 360Chrome's RAM consumption. Since then, I have been experimenting with rebasing browser DLL files. For Chrome/Chromium based browsers it was the chrome.dll, for UXP browsers and for Mypal 68 the xul.dll file. However, it was indeed me who casually remarked here first that rebasing the xul.dll file has a significant, positive effect on the RAM consumption of Mypal 68:
    1 point
  12. You didn't say that in this post. You only talked about a certain number of videos. Now suddenly, it's the duration. Somehow I get the feeling that these are just unsubstantiated theories and nothing more. But YouTube is a crappy interface and no option for browsers on my system. I use YouTube itself only on my Android tablet. Anyway! Opening videos via the legacy extension uTube is much, much, much better than the original YouTube interface. So, I am not interested in investigating the YouTube interface in UXP browsers.
    1 point
  13. I tried your first playlist in the most recent version of New Moon 28 using the legacy extension uTube and my mod uBlock Origin Legacy with several filter lists enabled. No such overlay popup after playing 8 and more music videos.
    1 point
  14. Yep! And they still work with my mod uBlock Origin Legacy. Why do you post an ad blocker for Chrome in a thread about legacy extensions for UXP browsers? Same applies to this extension. Not compatible with UXP browsers. Such recommendations should be done in corresponding threads. Otherwise it would be misleading. TBH, I have never seen such a message. I tried to reproduce your issue but I failed,. It doesn't seem directly related to the video in your screenshot. Here is my screenshot with your video in New Moon 28: No problem to play this video apart from the unfortunate fact that the music is terrible, which is of course always a question of taste.
    1 point
  15. My apologies for the late testing.. every time I get a good start on a project of mine something happens to delay it. Unfortunately this patch doesn't seem to work, it triggers an endless loop at the beginning of the second phase of SETUP. The text part of SETUP completes, the system reboots and shows "Installing Windows" and "39 minutes remaining" - but it never loads the first dialog box to click to continue. After a few seconds the screen goes all light blue and the machine reboots. This repeats on each reboot. No error is displayed.
    1 point
  16. This one - simply ignore, it's what all browsers that aren't supposed to run on XP write in the log.
    1 point
  17. Ordinary Chrome is free and has no timebomb, this one is paid, so no wonder in this trial version it has a timebomb. Any "fix" is considered to be a crack, so I doubt it will surface on MSFN.
    1 point
  18. Care to share what's so special about thorium? From what is known, it's still based on the last year chrome 109, the last officially supported.
    1 point
  19. I did a proper research before the posting, but you - obviously not, it's especially funny because it's on your linked pages. The issue was fixed in v28, more than 10 years and confirmed by the developers and checked by the testers. Proof at the end of the page. https://bugs.chromium.org/p/chromium/issues/detail?id=234318 "Confirmed that floppy is not accessed when chrome is launched." Verified in 28.0.1500.95 (Official Build 213514) You're not agree with the obvious facts? Then I'd like to hear your version on why the "bug" is there in the browsers that originate from the same place. EDIT: but please without fighting and accusing me of something I didn't do. Stick to the facts. So far, the facts point out to one place you're not happy to hear about.
    1 point
  20. More to the point, if you insist it's purely Chrome related, then it can be switched off in the flags, yet it doesn't work. For me it looks like an old bug is there for a purpose, but you're free to not agree with my opinion. Besides, judging by the comments in your multiple 360topics, you didn't solve it in (not saying which country) Chrome360. Why? I mean, if it's not a spying feature, but rather a well documented bug. Care to expand? thanks
    1 point
  21. How's Chrome from 10 years ago is relevant to this discussion? I too noticed the same spinning disks and floppy scanning with CatsXP (iit's from the same the country you prefer not to name). How would you explain that? Why do we not notice it in Supermium v115? Actually, it would've been reported immediately because Supermium is quite popular already. How would you explain that?
    1 point
  22. I also remember I observed similar behaviour with Opera (spinning up/scanning even sleeping HDDs) back in 2017, soon after the Norwegians sold Opera to the new owners in Asia. https://msfn.org/board/topic/184135-arcticfoxienotheretoplaygames-360chrome-v1352022-rebuild-3/page/20/#comment-1232307
    1 point
  23. ACPI often messes up with the device enumeration. A 9x PC with ACPI can have yellow marks in Device Manager whereas the same system without it, is perfectly fine. I do not see any benefits to use ACPI on 9x, even on period correct hardware...maybe hibernation? But hibernation on FAT32 is not a good idea anyways... It is not a coincidence that IBM specifically tells the user to install 98SE without ACPI as can be seen here in one of their files for their T4x series of ThinkPads, see here: https://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/tpisos98.txt http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/tpisos98.exe
    1 point
×
×
  • Create New...