monzero-core.git/src/common/threadpool.h, branch v0.17.1.0Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.17.1.02020-09-01T14:33:33Zthreadpool: guard against exceptions in jobs, and armour plating2020-09-01T14:33:33Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2020-08-12T22:13:29Zurn:sha1:6a37da837e1c936200f8d71a142973cc60b17b32
Those would, if uncaught, exit run and leave the waiter to wait
indefinitely for the number of active jobs to reach 0
Update copyright year to 20202020-05-07T02:36:54ZSomaticFanaticafdlkajdlfkj@aldkfjf.com2020-05-07T02:36:54Zurn:sha1:5ef0607da6042df51a57703bd223c5c8024741f6
Update copyright year to 2020
core_tests: reset thread pool between tests2019-11-10T12:58:49Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-11-10T12:58:19Zurn:sha1:27522aaa124a4a84091c3afaa85898dea2251c10
Avoids a DB error (leading to an assert) where a thread uses
a read txn previously created with an environment that was
since closed and reopened. While this usually works since
BlockchainLMDB renews txns if it detects the environment has
changed, this will not work if objects end up being allocated
at the same address as the previous instance, leading to stale
data usage.
Thanks hyc for the LMDB debugging.
Update 2019 copyright2019-03-05T21:05:34ZbinaryFatebinaryfate@users.noreply.github.com2019-03-05T21:05:34Zurn:sha1:1f2930ce0bec07e28958c059444151ad4968e1e6threadpool: allow leaf functions to run concurrently2018-06-26T21:15:22Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-04-26T10:44:47Zurn:sha1:2771a18e85bd91dd881f89f6c14d26cba35a1844
Decrease the number of worker threads by one to account
for the fact the calling thread acts as a worker thread now
threadpool: allow constructing an object, and misc tweaks2018-05-20T11:06:03Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-04-23T17:53:38Zurn:sha1:db55263b4c25a5014ce72aa1b601cfdebfe5d176
use unsigned int to avoid having to range check negative numbers,
use const where possible, don't needlessly create empty objects,
use std::move where possible
threadpool: catch exceptions in dtor, to avoid terminate2018-02-02T16:27:39Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-02-02T16:16:43Zurn:sha1:9b98a6ac8f750f5d786fe9a3a561373ca64e5049
If an exception is thrown, it is ignored. While this may hide
a bug, this should only be system exceptions in boost, which
is pretty unlikely. Morever, wait should be called manually
before the dtor anyway. Add an error message if the dtor has
to wait in case some such cases creep in so they get fixed.
Coverity 182538
Readd copyright starting date2018-01-26T15:03:20Zxmr-ericeric@moneroeric.com2018-01-07T23:55:52Zurn:sha1:84a7f6a4827f5baec6bb5cecbe11d4f61708b520Update 2018 copyright2018-01-26T15:03:20Zxmr-ericeric@moneroeric.com2018-01-07T05:05:16Zurn:sha1:18216f19dd479466cb7fd38f52d23bddfcfd4880Tweak concurrency limits2017-09-14T23:28:48ZHoward Chuhyc@symas.com2017-09-14T23:28:48Zurn:sha1:6d0ca7d11f18d1d842ec1ac639da4309ae41a83f
Create capacity for 2x max, but lie about it