Memory leak in Windows 8.10.8-45 version (Fixed now in 8.10.8-47)
Hello,
Since the last day or so, my system with 32 GB RAM has been experiencing out of memory issues. Following memory usage in Task Manager, the "Modified" memory composition rises steadily at the rate of approximately 2-3 Mb per second, until all memory is consumed and the system consequently crashes.
After a lot of trial and error, I have found that terminating the 1Password desktop application results in this excessive memory usage being freed. I have also noticed that the 8.10.8 upgrade was released in the past two days, which correlates with when this problem began occurring. Furthermore, from this thread, it appears that this was also noticed before then by those using the beta version.
Putting two and two together, there appears to be strong evidence of a memory leak being present in 8.10.8.
Apart from disabling the 1Password desktop application on startup and only running it when there is a need, what workarounds can I follow until this issue is (hopefully) patched?
1Password Version: 8.10.8
Extension Version: 2.12.0
OS Version: Windows 10 22H2
Browser: Chrome
Comments
-
This content has been removed.
-
I know the general policy of 1password is to not provide download links to past builds (only past versions like v7), but in this case it would be much appreciated to downgrade one build and prevent auto-update until the memory leak can be identified and corrected.
1 -
This content has been removed.
-
Hey folks,
We're investigating this as we speak and have a fix in progress. The latest nightly build has been confirmed by a few users to fix the issue, we're working on rolling this out to both stable and beta channels soon.
2 -
Hi again,
1Password 8.10.8-47 update is now available with the fixes. Please check for an update and let us know if it is working for you now.
2 -
This update keeps getting re-downloaded and installed perpetually. The app is never up to date. End up with many system tray icons. No issues with the app in 2+ years of using it, until this evening.
0 -
It's a caching issue, we're working to invalidate the CDN cache.
We released 8.10.8-47 but the CDN keeps serving -45 to you despite you already having -45.
Avoid checking for an update for a few hours.
0 -
The cache has been invalidated, it should now serve the 8.10.8-47 to you in a few minutes.
0