Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 09/04/2024 in Posts

  1. Screenshots? BTW, like I wrote, it's about the overall memory consumption, NOT speed.
    2 points
  2. It very well may be, it's a security flag that isolates site's processes, but I didn't suggest it.
    2 points
  3. You're welcome! --process-per-site is very important since it consolidates all numerous processes from a given website into one, hence the memory usage reduction. I posted this flag at MSFN several years ago, I remember VistaLover was confusing it with another flag --site-per-process, they are absolutely different. Seeing the memory leaks are starting to show them off literally on every site now, I indeed think, try it. Out of Memory - Google Maps, then Crash. https://github.com/win32ss/supermium/issues/847
    2 points
  4. optional --disable-low-res-tiling --wm-window-animations-disabled --disable-highres-timer (I like it, but you wrote it's somehow not fitting for XP 32bit).
    2 points
  5. So what stops you from checking? It will show "n/a", if you don't have one. IPv6 Address n/a https://browserleaks.com/ip
    1 point
  6. In my system with 1.5 GB RAM, every single megabyte counts. 350 to 450 MB is then a huge amount of RAM.
    1 point
  7. ... People, sadly, continue to do so now with Supermium/Thorium 32-bit on 32-bit XP SP3 (PAE-patched, a configuration the vendor NEVER supported) and have the audacity to create "issues" in the official trackers: https://github.com/win32ss/supermium/issues/846 IMHO, this type of users are beyond the point of realising they have a "serious problem" themselves...
    1 point
  8. Didn't you just contradicted yourself? This flag only has an effect if you are TAB HOARDING !!! No. If you open two or three tabs of the same domain to really work with them, then this has nothing to do with tab hoarding as they are closed immediately when all is done.
    1 point
  9. @reboot12 Thanks, I completely forgot to install Redistribuable C++ 2015 on this computer. ListDisk is working now !
    1 point
  10. Personally, I consider opening 15 MSFN tabs and probably many more tabs from other websites to be tab hoarding. IMHO, this kind of surfing behaviour might require professional treatment. BTW, I used to be afflicted with this disease for a while, but fortunately, as an autodidact, I was able to free myself from it. As for the chrome flag --process-per-site, I use it from the beginning and it really saves RAM. I consider this flag useful.
    1 point
  11. I test both Release XP & Release XP SSE work OK on SSE only CPU with vcredist x86 14:
    1 point
  12. Thanks so much for this info, This is indeed the solution!! Edit: Fun story, I'm banned from ElevenForum. Someone made some pretty nasty remarks about @Tihiy and I reported their post. I was suddenly banned for abusing the reporting system for one post. I guess it's okay there to make remarks about individuals nationality. It's a good resource but terrible moderation.
    1 point
  13. Hi @Tihiy, Maybe this flew under the radar, so I'd like to check again. Is SAB controlling the display of the list of open windows for an application icon in the taskbar? It seems that the width of the list is now dramatically smaller when there is a big number of windows for a single application. Before the list was wide enough to accommodate the longest window caption (or something like that). Thanks in advance!
    1 point
  14. This is a Windows 24H2 bug. Workaround: vivetool /enable /id:50557073,52110492 https://www.elevenforum.com/t/kb5041865-windows-11-insider-release-preview-build-26100-1586-24h2-aug-19.27764/post-490811
    1 point
  15. Probably because you added the switch after the switches' end. (on the screenshot). BTW, the order matters, at first I thought it was a placebo, but no,
    1 point
  16. As I already wrote here, I'm on vacation, no desktop PC around, besides - you mustn't compare on Windows 10, I wrote that, too. Only those OS that don't have the new memory functioning are relevant,
    1 point
  17. Correct. https://learn.microsoft.com/en-us/windows/win32/api/winreg/nf-winreg-reggetvaluea "Minimum supported client: Windows Vista, Windows XP Professional x64 Edition"
    1 point
  18. Thanks, sent the error report to the email. Oh indeed, works on XP x64, apparently they added that system call in it.
    1 point
  19. https://github.com/Blaukovitch?tab=repositories Christian name: Reinhard Residence: Austria (unsure about his descent, of course ) ; the account isn't currently banned, it does appear as the one account that provides bin-patched recent Google Chrome versions Win7-compatible ; but what has already been written about the RAM stands true: I am on Vista SP2 32-bit, BTW, so I've never used myself any of these "cra*ks" ...
    1 point
  20. I see it like this. If websites can't be loaded properly on my old computer under Windows XP, it's a sign that this website has disqualified itself for my system and now has the pleasure of making the acquaintance of my Android tablet. BTW, websites that take up hundreds of megabytes of RAM are simply rubbish in my world. Especially if they waste my precious RAM to show ads, offer meaningless things and collect user data.
    1 point
  21. Contrary to my original statement, I have tried to open the Facebook website in Thorium. Even there I am rewarded with a 100% CPU load, and my free RAM memory is being eaten up. The only thing that allows the page to load is using a mobile user agent. Unfortunately, many elements are then not displayed correctly. So, it remains the same. The FB page is just rubbish.
    1 point
  22. The reason lies around the PrefetchVirtualMemory and VirtualAlloc, since 110-112 the memory management code in Chrome was rewritten. This was the reason they dropped everything below 10, starting V110. PrefetchVirtualMemory (newly introduced function) glitches out on XP. The porters tried to replace it VirtualAlloc. No luck, as we see,
    1 point
  23. You can't compare browsers running on Win10 to any previous OS. I'll explain why. RAM management is different on Win10, it's the cause for the bug. They weren't able to fix it. The Russian guy (forgot his name, Blunauvich, was it?) he also acknowledged this huge memory leak, he couldn't fix it, then wrote about it to win32, the leak is still not fixed,
    1 point
  24. For the time being, try third party Instagram browsing sites, maybe? No login needed. https://www.pixwox.com/profile/INSERT_PROFILE_NAME_HERE/ Not sure whom this site belongs to, but works fine,
    1 point
  25. It should be mentioned at this point that I do not use uBO Legacy 1.16.4.35 at factory defaults. I use a different set of filter lists than the default one. Furthermore, I use additional lists, own rules and scripts. The initial, default setting is only a basic one and is not YouTube related. And I didn't get a video ad on the second video.
    1 point
  26. But now that various theories have been put forward about YouTube and overlay pop-ups with warnings to the user, I am happy to put forward my theory, which I will not verify or prove in any way. Google, and therefore YouTube, wants to make money. If users use the service over a long period of time without being a premium customer and yet without getting and watching any adverts, then this will certainly be registered by YouTube and therefore by Google in whatever way. These users must then have been using an adblocker the whole time and will eventually receive this overlay pop-up warning.
    1 point
  27. I'm glad I never used Telegram, the name sounded very awkward for me, even though I'm not a native English speaker.
    1 point
  28. Yes, I like this extension. It does its job, and the problem with the sporadic disappearance of the Clean Links' toolbar icon doesn't occur anymore.
    1 point
  29. New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20240824-3219d2d-uxp-2dea274c15-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20240824-3219d2d-uxp-2dea274c15-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20240824-3219d2d-uxp-2dea274c15-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20240824-d849524bd-uxp-2dea274c15-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20240824-d849524bd-uxp-2dea274c15-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20240824-d849524bd-uxp-2dea274c15-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20240824-d849524bd-uxp-2dea274c15-xpmod.7z Official UXP changes picked since my last build: - Issue #1810 - Implement {get|set}Transform with DOMMatrix arguments. (71bd54891a) - Issue #1810 - Allow superfluous [LenientFloat] extended attributes. (18f039543a) - Issue #1810 - Add DOMMatrix {get|set}Transform WebIDL interfaces (9d6ffb5814) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. Update Notice: - You may delete file named icudt*.dat inside program folder when updating from old releases. * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.
    1 point
  30. The good is that the user of New Moon and Serpent has still the choice, at least until now. All prefetching features can be manually disabled to ensure that uBlock Origin Legacy works properly, especially if the user notices interference. So, everyone can decide for themselves what is important to them.
    1 point
  31. Of course! There's a lot @Sampei.Nihira doesn't tell us here, or tells wrong. Now. we can only wonder why, does he simply entertain himself on MSFN? "Obviously MV3 has reduced performance." https://github.com/win32ss/supermium/issues/797#issuecomment-2295708131
    1 point
  32. I've had unpleasant experiences dealing with custom themes.
    1 point
  33. Thanks! How do I change the white background colour in folders?
    1 point
  34. Hi @xrayer Please provide a YouTube link where you noticed that the ad blocker was detected!
    1 point
  35. Exactly, despite my age, I use my father's era OS Vista! One of the reasons I joined.
    1 point
  36. 1 point
  37. "uBlock origin is definitely more powerful than Ublock Origin Lite. You can run both at the same time since they don't use the same API, but it's useless, especially on Brave." https://www.reddit.com/r/brave_browser/comments/1drsl17/ublock_origin_or_ublockorigin_lite_in_2024/
    1 point
  38. 1 point
  39. Thanks for asking! As long as no new errors occur and everything is running well, there is no need to update. I'm travelling on so many fronts that my time needs to be well managed. Or is something not working? I can't see any serious problems at the moment. uBlock Origin Legacy 1.16.4.35 is running fine here.
    1 point
  40. Thanks for getting back on topic. What's there you don't understand? There's real and there's fake. Like fake Supermium, for example.
    1 point
  41. Let me understand this correctly -- you're concerned about security implications of a protocol currently used by the majority of the world, this in the context of Windows XP (an OS that hasn't received security updates for roughly a decade)?
    1 point
  42. Recently got myself a rebranded WD (previously made by Hitachi), it's of course identical, 10TB WD 7200rpm. Very Noisy! Looks like it has "smart defrag" made by the device. I'm not happy with the purchase at all. Full specs: HGST WD Ultrastar DC HC510 10TB 7200 RPM SATA 6Gb/s 3.5" Helium Platform Enterprise Hard Disk Drive - HUH721010ALE604 (0F27606) Price approx 250-300 Euros.
    1 point
  43. @VistaLover, it turns out it was because I was at 100% zoom on my 1024x768 screen. It does appear when I zoom out a bit.
    1 point
  44. OK, since you can't add code when editing a post, here it is: [spoiler] [/spoiler]
    1 point
  45. It's undocumented, but you can try this:
    1 point
  46. New NewMoon 27 Build! 32bit https://o.rths.ml/palemoon/palemoon-27.9.7.win32-git-20191109-df039285e-xpmod.7z 32bit SSE https://o.rths.ml/palemoon/palemoon-27.9.7.win32-git-20191109-df039285e-xpmod-sse.7z 32bit noSSE https://o.rths.ml/palemoon/palemoon-27.9.7.win32-git-20191109-df039285e-xpmod-ia32.7z 64bit https://o.rths.ml/palemoon/palemoon-27.9.7.win64-git-20191109-df039285e-xpmod.7z source repo: https://github.com/roytam1/palemoon27 repo changes since my last build: - bump versions (58723f645) - ported bug1200802 (ef47f9b55) - import changes from rmottola/Arctic-Fox: - Bug 968520 - Explicitly specify the allocator for nsTArray_base functions. r=froydnj (8e11c1a0c) - Bug 968520 - Add fallible variant of nsTArray::SetCapacity. r=froydnj (3a33bc53e) - Bug 968520 - Add fallible variants of nsTArray::InsertElementsAt. r=froydnj (d52030d81) - Bug 968520 - Add fallible variant of nsTArray::EnsureLengthAtLeast. r=froydnj (7f22637b6) - Bug 968520 - Add fallible variant of nsTArray::SetLength. r=froydnj (a6f43b1b0) - Bug 968520 - Add fallible variants of nsTArray::ReplaceElementsAt. r=froydnj (e17169b21) - Bug 968520 - Add fallible variants of nsTArray::InsertElementAt. r=froydnj (0ed62209a) - Bug 968520 - Add fallible variants of nsTArray::AppendElements. r=froydnj (c4f4d2a1e) - Bug 968520 - Add fallible variants of nsTArray::AppendElement. r=froydn (3fbf72f7a) - Bug 1165729 - Remove unnecessary template declaration for fallible nsTArray::AppendElement. r=froydnj (f72cc5efd) - Bug 968520 - Make nsTArray::InsertElementSorted support moves. r=froydnj (217178725) - Bug 968520 - Add fallible variants of nsTArray::InsertElementSorted. r=froydnj (f99e300b9) - Bug 968520 - Add more fallible variants of nsTArray::InsertElementsAt. r=froydnj (218d4f025) (19841f19a) - addendum to git rev 19841f19a1e0fc573b99c2b56f280109786a79db, fix moz_malloc/moz_realloc/moz_free for our tree (3b174064e) - import changes from rmottola/Arctic-Fox: - Bug 1140264 part 1 - Avoid expanding auto-hidden ruby annotations. r=dbaron (5b6ddba10) - Bug 1140264 part 2 - Move and merge line breaking code in rbc reflow to reduce useless computation and fix undesired break point. r=dbaron (0d3aaad79) - Bug 1140264 part 3 - Rename IsInlineDescendantOfRuby to ShouldSuppressLineBreak and exclude rbc/rtc from it. r=dbaron (e929b296b) - Bug 1140264 part 4 - Reftest for this bug. r=dbaron (3aa19d44e) - Bug 1141842 - Add LastOptionalBreakPriority to nsLineLayout to simplify some code. r=roc (81cc1dcd0) - Bug 1137875 - Have the SharedFrameMetricsData hold a copy of the layers id. r=nical (81c657510) - Bug 1133237 - When transitioning from a shadow layer tree that has plugins to a tree that does not, make sure the old plugins get hidden properly. r=roc (11ff16c17) - Bug 1137875 - Have the LayerTransactionChild hold a copy of the layers id. r=nical (f9a090aad) - Bug 1137875 - Clear shared frame metrics objects associated with a PLayerTransaction when it is destroyed. r=nical (c5037ee27) - Bug 1119878 Part 1: Change SandboxTarget to hold sandbox target services to provide functions. r=aklotz, r=glandium, r=cpearce (7378d13e4) - Bug 1119878 Part 2: Change IPC code to hold ProcessID instead of ProcessHandle. r=billm, r=dvander, r=aklotz, r=cpearce (fa002f559) - Bug 1149971 Part 1: Follow-up to bug 1119878 to fix broken IPDL tests. r=dvander (76b843d43) and some lines of fix of toolkit/xre/nsEmbedFunctions.cpp after Bug 1119878 Part 2. (5ec13acbd) - import changes from rmottola/Arctic-Fox: - Revert Bug 1125848 - Consolidate PCompositor's creation-destruction logic because of 10.7 MacOS bustage (ceda5a133) - adapt assertion to be as introduced in Bug 1125848 (877071282) - Bug 1160190 followup. Make ServiceWorker actually disabled on mulet so we can reopen the CLOSED TREE. r=bkelly (1a03ee7c2) - Bug 1123846 - Restrict some activities to be provided by the system app r=ferjm (c7ca76805) - fix header include order (01b1289df) - Bug 1151644 - Don't disallow the basic compositor backend. r=jrmuizel (b70633afd) - Bug 1155823 - Properly shutdown the CompositorVsyncDispatcher. r=kats (a3dee13e8) - add gfxCrashReporterUtils as of 1180688 2015-07-13 (433fa6bdb) - Bug 1029673 - Correctly report OMTC compositing in crash reports - r=Bas (87fc22936) - Bug 1180688 - Detect whether the widget will be able to present frames with BasicCompositor on Mac. r=mstange (842ed309f) (eca52a3f8) - import changes from rmottola/Arctic-Fox: - Bug 1125848 - Consolidate PCompositor's creation-destruction logic. r=sotaro (bd9905d37) - Bug 1180688 - Reset the appropriate widget states if creating a compositor fails. r=mstange (461339a0c) - missing part of Bug 1119878 Part 2: Change IPC code to hold ProcessID instead of ProcessHandle. (631e112dc) (df039285e)
    1 point
  47. yes but not only that, my build also provides some functions they removed(e10s/webide/webextensions/etc.), and maybe additional fixes.
    1 point
  48. alright renamed to foxyproxy_standard-4.6.5-pm.xpi okay it will check app.feedback.baseURL as well if palemoon is not found in browser.search.searchEnginesURL.
    1 point
  49. New NewMoon 27 Build! 32bit https://o.rths.ml/palemoon/palemoon-27.9.6.win32-git-20191102-13f9e7fee-xpmod.7z 32bit SSE https://o.rths.ml/palemoon/palemoon-27.9.6.win32-git-20191102-13f9e7fee-xpmod-sse.7z 32bit noSSE https://o.rths.ml/palemoon/palemoon-27.9.6.win32-git-20191102-13f9e7fee-xpmod-ia32.7z 64bit https://o.rths.ml/palemoon/palemoon-27.9.6.win64-git-20191102-13f9e7fee-xpmod.7z source repo: https://github.com/roytam1/palemoon27 repo changes since my last build: - import changes from rmottola/Arctic-Fox: - pointer style before patch (e67d52f86) - Bug 1141067 - byte operations on x86/x64. r=sunfish (072056e84) - Bug 1138348 - byte array test cases. r=h4writer (9495e2804) - pointer style (3a458b6e8) - Bug 1138348 - byte ops on x86_64. r=h4writer (e5ad2140a) - Bug 1134791 - Show the testharness.js output when the browser remains open after running the test; r=bz (27fedb2ed) - Bug 1137515 part 2 - Change to media [partially applied] (203599e89) - Bug 1125848 - Consolidate PCompositor's creation-destruction logic. r=sotaro (022a02f8a) - Bug 1137291 - avoid clobbering an input register. r=h4writer (9d742a093) - Bug 1136352 - Fix RemoveTextureAsync handling r=nical (172b17d45) - Bug 1139935 - Re-enable RemoveTextureFromCompositableTracker r=nical (ea9735be9) (ddef3772b) - import changes from rmottola/Arctic-Fox: - Bug 1090583 part 2 - Fix the property count check in MonitorAssign to check the actual count instead of the capacity. r=bhackett (3f1daa802) - Bug 1090583 - Fix a pre-existing issue with MLoadElementHole and negative index checks. r=bhackett (1278f0b1a) - Bug 1141190 - Remove docshell/test/moz.build; r=mshal (641a1716f) - bug 1161402 assert that some public methods are called on reader task queue r=cpearce (c8355d774) - bug 1161402 assert that public methods are not called after shutdown r=cpearce (07db4d8d0) - Bug 1137906 - Shutdown cached children when shutdown the document. r=surkov (45e3894eb) - Bug 1141676 - Reftest for sizing of synthetic sub/superscript glyphs r=jdaggett (eab4327fb) - Bug 1141748 - Do not use non-standard flag argument of String.prototype.replace in CSSUnprefixingService.js. r=dholbert (631be2090) - Bug 1134537 - Delete GnomeVFS extension. r=roc (cd03d727a) - Bug 1063880 - Allow a --disable-compile-environment to go through a full mach build. r=mshal (67ef7e874) - Bug 1063880 - Do not emit Linkable-derived objects when COMPILE_ENVIRONMENT is not set. r=mshal (7e4b1f82a) - Bug 1141660 - Always export memalign from jemalloc, even on Windows. r=njn (b625580bf) - Bug 1135354 - Crash/Hang when clicking URL with a huge length r=mcmanus (84b653c37) - remove errneously commited patch (39668bbff) (13f9e7fee)
    1 point
  50. Addition: The above procedure may only be relevant for those who have not yet posted in this new thread; once one posts here for the first time, and according to one's own forum preferences, a "Notify me of replies" switch button should be present to the far left of the "Submit Reply" button - in the bottom of your newly composed post - turned to ON by default...
    1 point
×
×
  • Create New...