Hi, Do you have any idea of the incriminating commit in opendht, and/or conditions in which this bug triggers? Is it purely caused by opendht, or does it depend on the version of ring?
On Archlinux, the current version of the opendht package I maintain is 0a4195ae08f7fb1a7a215eb0e7542f9ad33ca80d, and a user reported a similar issue. But it does not trigger on my system. Thanks, Baptiste On Thu, Dec 10, 2015 at 07:01:10PM -0500, Guillaume Roguez wrote: > Hi, > > We've found that a recent version of our DHT library may cause some > hi-traffic on your network and may saturate your computer ressources. > > We've solved the problem on Ring by reverting to an older version (of > OpenDHT) to not introduce this regression, until we found the exact issue. > The problems has not been seen with this fix so we recommand, if you have > updated Ring during the day of 10 december, update it now as > our recent builds have the fix. > > Thanks, > Guillaume > Ring Project Director > _______________________________________________ > Ring mailing list > Ring@lists.savoirfairelinux.net > https://lists.savoirfairelinux.net/mailman/listinfo/ring
pgp7ZETX7EicP.pgp
Description: PGP signature
_______________________________________________ Ring mailing list Ring@lists.savoirfairelinux.net https://lists.savoirfairelinux.net/mailman/listinfo/ring
