For the issue like T4255: gpg-agent: "<gcrypt> Cannot allocate memory" with 10 threads decrypting OpenPGP, it might be worth to limit number of active connections (to let wait clients) of gpg-agent.
Since feature like this is racy, we need to review the changes carefully.
And we also need to consider adding event to wake up on Windows.
Besides, we need to consider putty support on Windows.
Details
Details
- Reviewers
- None
- Commits
- rKLEOPATRA5e9d402be380: Yet another place with deprecated API
Diff Detail
Diff Detail
- Repository
- rG GnuPG
- Lint
Lint Skipped - Unit
Unit Tests Skipped
Event Timeline
Comment Actions
This is an experimental patch. So, I just reuse SIGUSR1 to wake up "select"-ing thread by kill(2).
I put limit-active-connections 2 in gpg-agent.conf for the test with run-threaded of gpgme.
Comment Actions
I don't think that this is a good solution for a problem we could solve much easier but fear to do that due to kind of crypto politics.