Firefox is brcoming so 'buggy', i now only jze js as a backup for Bfavd. Pity, it jsex to be ghd BEST.
Not sure if if this is a settings issue. All good, except the Status Bar and progress bar do not show progress activity during prompted cleaning of all accounts, as befo… (read more)
Not sure if if this is a settings issue. All good, except the Status Bar and progress bar do not show progress activity during prompted cleaning of all accounts, as before. I cannot tell if it's still working or not, or if I can close the program without crashing or corrupting something. I am guessing it's working as the HD light is busy. Eventually (some accounts are large) the status bar indicates it compacted to save ___MB. Version 152.0 on Windows 10, supported.
It's very odd. Normally moving an email, say from the Inbox to the relevant year's archive, takes "no time at all". Which is true for all the mailboxes shown on the attac… (read more)
It's very odd. Normally moving an email, say from the Inbox to the relevant year's archive, takes "no time at all".
Which is true for all the mailboxes shown on the attached screenshot, EXCEPT for the four at the bottom. Moving even one message from Inbox to Yiddish can take ten seconds or longer (with the dreaded "Not Responding" occasionally). Moving something in the opposite direction is also screwy, only from those four.
I had thought that it was because they're rather large. This first started when there were just Yiddish and MSW, and I split off most of the earlier years into the archives shown. To no avail.
It's only an annoyance, but I'm puzzled about how such a thing could happen.
Also very slow tagging or untagging a message just in those mailboxes.
We have an asp.net Blazor SPA (server side Blazor) that dynamically generates components within the page. Over time, there is a very large RAM leak under document-shared… (read more)
We have an asp.net Blazor SPA (server side Blazor) that dynamically generates components within the page. Over time, there is a very large RAM leak under document-shared that climbs until the windows are closed.
We have tried various firefox configurations to try and either disable this shared storage as well as limit but with no luck. THe memory allocation is in GB of RAM space and cannot be limited or reduced until the window itself is closed/restarted.
Research online indicates this can happen due to colocated stylesheets and how firefox wants to cache styles aggressively. Adjustments to move stylesheets does not appear to help.
What configurations can I use to help prevent/reduce this high RAM usage? This does not occur in Chrome or Edge, I cannot replicate this well under FireFox for Windows.