Leaderboard

Still not clear? Strange, @NotHereToPlayGames understood very well. Most likely non-English users. Then hold on, much harder text ahead.., Blurry (definition). adjective Full of blurs; blurred. Similar: blurred Not clear, crisp, or focused; having fuzzy edges. Not clear, not with well-defined boundaries. The GNU version of the Collaborative International Dictionary of English • More at Wordnik. Courtesy of https://duckduckgo.com/ Search Assist Blurry means lacking definition or focus, often used to describe an image that is not clear or sharp, having fuzzy edges. It can also refer to something that is unclear or lacks well-defined boundaries in a figurative sense. Wiktionary Reverso

reverting changes in #2895 seems help. now 32bit builds are being compiled and same filename archives will be replaced later. EDIT: all today's 32bit build archives are updated.

heard similar report on different websites but both of them are not reproducible here. EDIT: try translating in bing translator, and it does happen: > mozjs.dll!js::jit::BacktrackingAllocator::tryAllocateRegister(js::jit::BacktrackingAllocator::PhysicalRegister & r, js::jit::LiveBundle * bundle, bool * success, bool * pfixed, mozilla::Vector<js::jit::LiveBundle *,4,js::SystemAllocPolicy> & conflicting) Line 1395 C++ [Inline Frame] mozjs.dll!js::jit::BacktrackingAllocator::tryAllocateNonFixed(js::jit::LiveBundle *) Line 1221 C++ mozjs.dll!js::jit::BacktrackingAllocator::processBundle(js::jit::MIRGenerator * mir, js::jit::LiveBundle * bundle) Line 1291 C++ mozjs.dll!js::jit::BacktrackingAllocator::go() Line 835 C++ mozjs.dll!js::jit::GenerateLIR(js::jit::MIRGenerator * mir) Line 1928 C++ mozjs.dll!js::jit::CompileBackEnd(js::jit::MIRGenerator * mir) Line 1998 C++ mozjs.dll!js::HelperThread::handleIonWorkload(js::AutoLockHelperThreadState & locked) Line 1554 C++ mozjs.dll!js::HelperThread::threadLoop() Line 1918 C++ [Inline Frame] mozjs.dll!js::detail::ThreadTrampoline<void (__cdecl&)(void *),js::HelperThread *>::callMain(mozilla::IndexSequence<0>) Line 233 C++ mozjs.dll!js::detail::ThreadTrampoline<void (__cdecl&)(void *),js::HelperThread *>::Start(void * aPack) Line 227 C++ but javascript related changes only happened in https://repo.palemoon.org/MoonchildProductions/UXP/issues/2895 which doesn't look like what shows in malloc-trace shown above. and when memory usage is high (but not too high to be crashed), about:memory shows high heap-unclassified and later it gets reclaimed. hmm, so strange. EDIT2: another one to be suspected is expat library update: https://repo.palemoon.org/MoonchildProductions/UXP/issues/2889

Aliasing https://en.wikipedia.org/wiki/Aliasing

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20260117-3219d2d-uxp-aace8fa8c0-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20260117-3219d2d-uxp-aace8fa8c0-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-20260117-3219d2d-uxp-aace8fa8c0-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-20260117-d849524bd-uxp-aace8fa8c0-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260117-d849524bd-uxp-aace8fa8c0-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260117-d849524bd-uxp-aace8fa8c0-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20260117-d849524bd-uxp-aace8fa8c0-xpmod.7z Win7+ x64 AVX2 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20260117-d849524bd-uxp-aace8fa8c0-w7plus-avx2.7z Official UXP changes picked since my last build: - Issue #1636 - Part 1 - Decouple Gio from GConf and always build it with GTK (fc78eec911) - Issue #1636 - Part 2 - Disable Gconf by default (990f256885) - Issue #1636 - Part 3 - Remove Gconf (b04e3d93c9) - Issue #2895 - Part 1: Replace XorShift128+ with Xoroshiro128++ (d4341ea07a) - Issue #2895 - Part 1b: Update license block. (d23afa84e5) - Issue #2895 - Part 2: Remove incorrect debug asserts. (5a0f190104) - Issue #2895 - Part 3: Add manual test. (75ec48bc41) - Issue #2889 - Part 0: Relocate Mozilla-specific files from Expat source. (b81b97ee47) - Issue #2889 - Part 1: Prepare Mozilla's changes and extensions for Expat 2.6.4. (9567601675) - Issue #2889 - Part 2: Import Expat 2.6.4 source. (9ade98b4fc) - Issue #2889 - Part 3: Apply Mozilla's patches to Expat 2.6.4. (0b9e221b14) - Issue #2889 - Part 4: Fix build and runtime issues. (a2f8e66162) - Issue #2889 - Follow-up: Avoid conflicts with system version of libexpat (e0f8acddc7) - Issue #2889 - Follow-up: void methods shouldn't return a value. (8956c61187) - Issue #2889 - Part 5: Rewrite patches for Expat 2.7.3. (a730f838c8) - Issue #2889 - Part 6: Import Expat 2.7.3 source. (d2acec73f7) - Issue #2889 - Part 7: Apply patches to Expat 2.7.3. (ca2ef5184a) - Issue #2889 - Follow-up: Allow generate_hash_secret_salt to be used. (acefed74fe) - Issue #2889 - Follow-up: Adjust Expat 2.7.3 local patches for removal of 3rd patch. (034eeaff97) - Issue #2889 - Follow-up: Remove fix for BZ 569229. (493169e227) - Issue #2895 - Follow-up: Fix JIT code generator for 32-bit targets. (d6e9c4d85b) - [gfx] Be more explicit when converting to cairo formats. (f6d18c7d78) - [gfx] Use better types for cairo image surface manipulations. (6ca8cf782b) - [DOM] Check worker script size (d8f7202951) - [Auth] Only set GSS_C_DELEG_FLAG flag when we confirm server supports delegation. (5321363a1b) - [NSS] Update NSS (464b24c608) - [XPCOM] Add hashkey helper classes for future use. (7b9eda3f69) - [gfx] Add some additional sanity checks to cairo surface creation. (3aff60e443) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. My changes picked since my last build: - application: remove gio from MOZ_EXTENSIONS_DEFAULT (69c17afbe0) - htmlparser: break when infinite loop happens (8201dadf41) Update Notice: - You may delete file named icudt*.dat and icu63.dll 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.

You must have misunderstood something. Panda only needs ProxHTTPSProxy to activate the Panda account. After that, the proxy settings in Panda can be deleted and the proxy closed.

Here is a quotation from my main article: And I should add that it is very important to delete all dummy cerificates in the Certs folder when the cacert.pem file has been updated. And you won't lose anything. The dummy certificates will be generated the next time when connecting to servers. BTW, you are using the proxy system-wide. That was what I asked you in an earlier post. I personally do not.

@Dave-H Do you regularly maintain your proxy? For ProxHTTPSProxy to function properly, it must be maintained. From time to time, the Certs folder must be emptied, and the cacert.pem file must be updated. Only then will it function properly and can connect to the Panda servers. Then you will finally see the connections established to their servers.

I can't confirm this statement. When I installed Panda Dome 21.01.00, I was only able to activate the Panda account with the help of ProxHTTPSProxy, using the necessary proxy settings in Panda. Connections to Panda's servers were immediately visible in the proxy console.

Here is a short report on the Panda Dome version 20.02.01 currently installed on my computer. This version runs very well under Windows XP without any performance problems. This Panda Dome version also does not significantly delay Windows startup. It only takes approx. 2 min. This is a good value for my old box. However, I have not yet been able to solve one problem. The application background remains green. No images can be loaded. Although it's not important, I don't understand why this is the case. Here is a screenshot of this issue and one taken from the settings where the image can be selected: This issue has been the case in all versions of Panda Dome (18.07.04, 20.02.01, 21.01.00, 22.00.00, 22.02.01 and 22.03.05) installed on my Windows XP partition with all POSReady updates. This issue doesn't exist on my Windows XP partition without POSReady updates.

Very blurry, eye killing, over aliased, pixelated fonts, super hard to read.

No, It's a lot of posts I still didn't "like". But then again, it's so off-topic, but still you're allowed to post off-topic, so why would I not be allowed to do the same? add No off topic from me again because I respect the forum users!

I believe in those numbers, as I already stated, I don't trust someone will perform the fake scheme you just described. People have things in life, apart from the forum, you know! Besides, it's easy to check, as I already stated, too! So what? It's my business in what to believe. But at this point, it's too obvious you're very annoyed with someone else's fame. I also think there was a hidden reason to disable topic views. As already stated by @Monroe. Otherwise they would've gotten them back by this time already.