Mypal68
Mypal68 copied to clipboard
Feodor2
Add-ons Manager - Manage Your Extensions - New issue
Hi Feodor2. When clicking an add-on in the Add-ons Manager, a new problem occurs in your latest version 68.12.4b. Instead of showing the page containing Details and Permissions, I get this error:
The address wasn’t understood. Mypal doesn’t know how to open this address, because one of the following protocols (addons) isn’t associated with any program or is not allowed in this context. You might need to install other software to open this address.
Never seen before! The menu item More Options works as expected. In your previous version 68.12.3b, there was no such issue. I tested it with two different profiles. I seriously hope the problem won't be on my side, what would mean, I'd have an issue in my system. 
Cheers, AstroSkipper 
I did not reproduce this, lets somebody else check.
Hi Feodor2, I created a new profile, deactivated my style sheets settings, and I found the cause of this problem. I prefer using Mypal 68 in single process mode, and therefore, I set browser.tabs.remote.autostart to false. When doing this, your recent version 68.12.4b shows the described misbehaviour above. Something must have been changed since previous release 68.12.3b. In this previous version, I didn't observe the issue. Hope, this will help you find a solution. Without setting the variable browser.tabs.remote.autostart to false, Mypal 68 is nearly useless for me in my system with only 1.5 GB RAM (and it can't be extended). In multiprocess mode, Mypal's RAM consumption is infinite, and for people with low system resources not suitable.
Cheers, AstroSkipper 
Try this little application.
https://www.rizonesoft.com/downloads/firemin/
It reduces the RAM usage of Firefox (or Mypal...) I didn't really think it would work without tremendously slowing down the browser but for some strange reason, it really works very well. At least on a relatively new computer. My RAM usage on Firefox 91 dropped to about 400MB max, even with HD youtube videos playing. I've also tried it with Mypal. It works as well. However, there might be some audio dropouts in videos when "Enable extended processes" is ticked.
I have no clue how well it works on ancient computers like yours but don't give up too soon. You can try different settings (you'll see it if/when you install it) and maybe it'll help to reduce the RAM usage drastically without slowing down Mypal noticeably.
Try this little application.
https://www.rizonesoft.com/downloads/firemin/
It reduces the RAM usage of Firefox (or Mypal...) I didn't really think it would work without tremendously slowing down the browser but for some strange reason, it really works very well. At least on a relatively new computer. My RAM usage on Firefox 91 dropped to about 400MB max, even with HD youtube videos playing. I've also tried it with Mypal. It works as well. However, there might be some audio dropouts in videos when "Enable extended processes" is ticked.
I have no clue how well it works on ancient computers like yours but don't give up too soon. You can try different settings (you'll see it if/when you install it) and maybe it'll help to reduce the RAM usage drastically without slowing down Mypal noticeably.
Thanks for your reply! Firemin is already present for years. But it won't help in the case of Mypal 68. On my old machine, Mypal 68 can be used only in single process mode, otherwise I can only open two tabs at most. More recent browsers are awful in RAM consumption. My only hope is that Feodor2 can revert the code associated with this issue as it was in the previous version 68.12.3b.
Cheers, AstroSkipper 
I switched browser.tabs.remote.autostart and still did not get the error. You may do this: launch the browser - open the console - there will be errors of course - ignore them - open the errorful addon options - look for new errors in the console - tell me what is the addon and put the error data.
Here is a screenshot after setting browser.tabs.remote.autostart to true and restarting the browser:
In this case, the only message I can see in the web console is "Stylesheets without CSSOM changes reparsed to check for errors. Refresh the page to also see errors from stylesheets changed from CSSOM and from style attributes. 4"
And now a screenshot after setting browser.tabs.remote.autostart to false and restarting the browser:
In this case, the only message I can see in the web console is "Stylesheets without CSSOM changes reparsed to check for errors. Refresh the page to also see errors from stylesheets changed from CSSOM and from style attributes. 3"
Tested in a fresh profile with only one extension installed. What kind of extension, doesn't matter (but if you still want to know, it's the extension Forget Button - Clean your Browser). Clicking in the Add-ons Manager onto the extension's entry, leads to this issue when the variable browser.tabs.remote.autostart was set to false. This issue can be reproduced in each of my profiles. Unfortunately, I can't see further error messages in the web console. But I also have to state that normally, I don't use the web console due to no need, and maybe I do something wrong. Therefore, please, let me know what I can do to provide more data associated with this issue if you are not able to reproduce it!
Kindest regards, AstroSkipper 
I just tried this and I can't confirm this problem. The settings page of the Addon (I even installed the same one) is still displayed normally after setting browser.tabs.remote.autostart to false.
Very strange.
Thanks, NoNameNeeded2, for your reply and test! I totally agree with your statement that this is a bit strange. Therefore, I checked again and did a deeper investigation of this issue. I examined all variables and combinations of them in about:config, but without any success. But Goddess Fortuna unexpectedly came to my aid. Here are the instructions to reproduce the issue ultimately (at least I do hope so):
- Set the variable browser.tabs.remote.autostart to false.
- Restart the browser.
- Open Add-ons Manager and ensure you see the list of the installed extensions.
- Now, do not click onto the image of each extension outside left, but onto the extension's link right next to it.
- Now the issue should occur, actually.
If you click onto the image of each extension outside left, the page with the Details and Permissions will be shown as expected. My personal conclusion: If the variable browser.tabs.remote.autostart is set to false, i.e., using single process mode, the extension's link isn't associated as it should be. When setting back the variable browser.tabs.remote.autostart to true, i.e., reverting to multiprocess mode, and restarting the browser, the extension's link is associated as it should be. Hope, this will help you, Feodor2.
PS: In my example of the extension Forget Button - Clean your Browser, the corresponding link is addons://detail/{13ea5d17-aa13-474a-b8cd-891073b53c66} which is not associated properly in single process mode. The same for all other installed extensions. Furthermore, I could reproduce it in all my profiles.
Kindest regards, AstroSkipper
Ok, now I can confirm it.
It's very strange, though. Sometimes the problem occurs when you click on the name of the addon (it is in fact more likely to occur when you click on the name than on the decription below or the picture beside the name) or sometimes it doesn't occur. All the other stuff (themes, settings) won't be available either when the problem occurs.
But you can just close the tab and re-open it and avoid to click on the name.
Ok, now I can confirm it.
Hi NoNameNeeded2, thanks for your confirmation! I am glad you could reproduce it finally.
But you can just close the tab and re-open it and avoid to click on the name.
Reloading the page works either. Of course, avoiding a click on the extension's link is a suitable, temporary solution. In the previous release 68.12.3b, this issue didn't occur. Of course, I hope I didn't click the extension's image the whole time only, but I don't believe that. The probability for such an event is very small, nearly zero :-). In my opinion, something in the code must have been changed since then. Anyway, I am really glad that I am not the only one observing this issue.
Cheers, AstroSkipper
I'm afraid I'm not Feodor.
You're right. Sorry for the confusion! 
Unfortinately, I was a bit overtired. I thought I would reply to Feodor2. But there is only one Feodor2, of course. I corrected the post above. In any case, thanks again for your efforts and the time you spent in testing my problem! I really appreciate that!
Cheers, AstroSkipper
The protocol addons:// seems broken with single process. Interesting what it supposed to do and why it works when click image even in the single process. Anyway this is a minor error i shall not hurry to fix it.
The protocol addons:// seems broken with single process. Interesting what it supposed to do and why it works when click image even in the single process. Anyway this is a minor error i shall not hurry to fix it.
Of course, it's just a minor bug. Other bugs are certainly more important. Regarding the error, I have the following theory. When clicking the image, maybe, you don't call up the protocol addons:// directly, its link can't be seen down below, and that might be the reason it still works in single process mode. We needn't forget that the call up by the menu item More Options works either. But calling up the addons:// link directly instead, its link can be seen down below, will fail due to the broken protocol in this mode. Seem, presumably, to be different call ups. In any case, thanks for your reply!
Cheers, AstroSkipper