Closed tourtools closed 3 years ago
Thanks @tourtools - The reason for this is the fact that Buttercup core (5.2.1) has a very dramatic memory leak in its auto-update function, which causes large amounts of objects to be addressed and tied-up in permanent references of each other, so GC never takes care of them.
I'm currently addressing this in the core..
The base issue will be dealt with here: buttercup/buttercup-core#282
thanks @perry-mitchell for the prompt response, I'll follow the core issue 282
So it seems like the issue is solved for me, though I haven't tested for many hours. The memory and CPU consumption is far better than it was, and I've fixed a number of poorly-performing vault item lookups in the core library. I'm about to do a release - v2.22.0.
tested with Brave with the new plugin/core v 2.23.0 and the results are quite the same, maybe it takes a little bit more time to get stuck but after a while the process reach the 100% of CPU and the plugin became unavailable:
FYI
Performance still bad for me in 2.23.0 (i.e. Vivaldi) but it's hit and miss
Will keep an eye on CPU next time as I imagine that may explain the hit and miss nature
Sincerely
I think this issue or https://github.com/buttercup/buttercup-browser-extension/issues/368 should be reopened
When CPU is high (i.e. >10%) the popup is delayed:
Hope this helps
Sincerely
software - OS: Apple, macOS, 10.15.7 (19H2) software - application: Vivaldi, 3.3.2022.47 (Stable channel) (64-bit) software - extension: Buttercup, 2.23.0
@ldexterldesign Good point, I've reopened that issue.
after about 5 minutes Buttercup extension became unaccessible, its process sucks 100% of CPU:
after killing the process and reloading the extension it follows the same behavior again and again: