AstroSkipper

I can remember very well that there was a problem with the sporadic disappearance of the Clean Links' toolbar icon in the past. This seems to be fixed in CleanLink2 as far as I can tell at the moment. In any case, I have installed this version and will see how it behaves.

As I already mentioned before, I can't confirm your issue with the logger in uBlock Origin 1.57.2 in single-process mode. Here is a screenshot as a proof:

Thanks for testing! I'm glad it works for you. But if you look at my screenshots above, you'll see that I actually have problems with uBlock Origin 1.57.2 in multi-process mode. And I'm not imagining them. BTW, I did a fresh install of Mypal 68.14.0b with a fresh, untouched profile. Maybe, this multi-process mode is not compatible with every hardware? Or do you use other settings for multi-process mode as your default ones?

Blame is not uploading, so what type of the crash do you get? The kind of crashes I experience is always an immediate closing of the browser when I click on links in my logged-in account on Codeberg. Some clicks here and there, and all of a sudden, the browser closes without any error message. And that only in single-process mode. I would like to provide more information but there is none I am aware of.

I used Pure URL in the past. And long time ago, the extension Clean Links. CleanLink2 seems to be a fork of Clean Links. So, thanks for the hint! I will try this forked version next time.

Since I created an account on Codeberg, I get these crashes only in single-process mode, They occur absolutely randomly without uploading any file. It is enough to click some links here and there, and the browser crashes immediately without any message. And it never happens with the same link. Very strange!

Thanks for replying! First, I tried a basic installation, without any further settings or additional filter lists in Mypal 68.14.0b using the default multi-process mode. Only the pre-selected filter lists were loaded. So at first sight, all seemed to be fine. That means, to answer your question, the vanilla install works. But if I enable the default filter list AdGuard - Ads, all is over. Here is a screenshot showing this error state: Same when enabling the default filter lists AdGuard Tracking Protection or AdGuard URL Tracking Protection. Endless loading of these lists. The complete uBlock Origin installation becomes inaccessible. Even a restart can't do anything. The GUI of uBlock Origin's dashboard page is then completely broken. Here is a screenshot showing the broken tab Filter lists: Therefore, I had to uninstall it due to a complete breakage in accessing other websites by the browser. BTW, you mentioned my reported issue here https://github.com/Feodor2/Mypal68/issues/426. Unfortunately without the important information that this issue only happens in multi-process mode but not in single-process mode. Maybe, you can add this missing information. Is anyone here who can or cannot confirm this issue I observed? Regarding your statement that the logger doesn't work in single-process mode, I can't confirm that. Working here as far as I can see. Tested in uBlock Origin 1.57.2. Anyway! uBlock Origin 1.57.2 is fully working in Mypal 68.14.0b if configured in single-process mode but not in multi-process mode. I would therefore assume that something is wrong with the multi-process mode, or the default configuration of the multi-process mode is somehow problematic for uBlock Origin 1.57.2. At least, on my Windows XP computer, even with hardware acceleration disabled. Greetings, AstroSkipper

Update notification Mypal 68.14.0b has been released on Codeberg.org, Therefore, I updated the first post of this thread. In this version, the automatic update of extensions is not enabled. If you are interested in re-enabling this feature, simply read this instruction: Restoring the manual and automatic update function for extensions in Mypal 68.13.3b Altough written by me for an older release, this instruction is still valid for Mypal 68.14.0b. Cheers, AstroSkipper

FYI, this issue still exists in Mypal 68.14.0b. Just tested. Nevertheless, thanks for your new update and the changes to JavaScript in terms of local time and time zone! The functions .toLocaleString(), .toLocaleDateString() and .toLocaleTimeString() are working great now.

@feodor2 I have installed your latest version Mypal 68.14.0b and tried it in multi-process mode. Unfortunately, I had big problems with uBlock Origin, no matter if the latest version 1.57.2 or the last version 1.46 which was still compatible with FF 68. It was no longer possible to load additional filter lists, and the extension was only in an error state. uBlock Origin became inaccessible, and the browser even hung after closing. Especially when I tried to load the default filter list AdGuard - Ads. I also disabled the hardware acceleration but unfortunately without any effect. Something is seriously broken. And it seems to be the same in the previous release Mypal 68.13.9b also only in multi-process mode. However, no problems in single-process mode. Any ideas? Or am I the only one having such problems?

Ok! I checked my system once again. In my Windows XP main partition, I unfortunately discovered that one of four registry keys relating to the region and language options had disappeared. No idea why. However, the time and time zone display was still intact. Fortunately, I have a second Windows XP partition from which I was able to export the missing key HKEY_CURRENT_USER\Control Panel\International and import it into my main partition. Now, all is working again. This fixing has actually led to a change in Firefox ESR 52.9.0. Now I also get the correct time and time zone displayed there:

All is correct. Do you really think that I wouldn't have checked that first of all? So, the question is what did you and @UCyborg do that makes Firefox ESR 52..9.0 show the correct time and timezone?

On the other hand, the following JavaScript command returns the correct time zone including DST in Firefox ESR 52.9.0: new Date().toTimeString().slice(9); "GMT+0200" or new Date().toString(); "Mon Apr 22 2024 20:45:37 GMT+0200" or new Date().toDateString(); "Mon Apr 22 2024"

I found a further JavaScript command to get the correct, local time including DST in the web console of New Moon 28, Firefox ESR 52.9.0 and Serpent 52 probably too: new Date().toTimeString().slice(0,8); returns the correct,, currently local time at the moment: "19:41:01"

Here, I get the same as @AstroSkipper, so "ETC/GMT-1". Here unfortunately not as I already mentioned before: