Generating keypair leaks memory
See original GitHub issueIt’s possible that nacl.box.keyPair()
leaks memory every time it’s called. In KeePassXC-Browser that functions is called repeatedly in a reconnect situation.
Details in the related issue: https://github.com/keepassxreboot/keepassxc-browser/issues/1113
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
IJ44040: GENERATING DIFFIE-HELLMAN KEY PAIRS ...
Generating DIffie-Hellman KeyPairs repeatedly, using IBMJCEPlus, causes a small memory leak. The small memory leak occurs when internal data structure used ...
Read more >Developers - Generating keypair leaks memory -
It's possible that nacl.box.keyPair() leaks memory every time it's called. In KeePassXC-Browser that functions is called repeatedly in a reconnect situation ...
Read more >On-board RSA key generation on Cyberflex Access 64K V2 ...
On-board RSA key generation on Cyberflex Access 64K V2 / Memory leak? ... instantiate a KeyPair object on which genKeyPair() can be called....
Read more >Memory leaks on firefox (using the extension) · Issue #1113
Overview keepassxc extension on firefox has severe memory leaks crippling the system hard and sometimes bringing firefox to a crash if i ...
Read more >ios - Keychain/Foundation memory leak
I've founded that sometimes getStringForKey: returns nil (maybe 1 time of 100). Profile shows me memory leaks every time i call this method....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@CMEONE You’re correct. I made an example extension and it doesn’t have the memory leak. So this is definitely a KeePassXC-Browser issue. Something is done in a way that the GC doesn’t trigger. Sorry for the inconvenience. Closing the issue.
I tried my example with a “global” variable, but that didn’t reproduce the issue. Thanks for the tips.
EDIT: Another user did a performance analysis in the original issue and it shows the following: https://user-images.githubusercontent.com/23653/100321818-f6c67580-2fcb-11eb-9449-dfcdae4c3f10.png