monzero-core.git/src/common/threadpool.cpp, branch mainMonzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=main2022-03-04T05:59:20ZCopyright: Update to 20222022-03-04T05:59:20Zmj-xmrmjxmr@protonmail.com2022-03-01T11:16:17Zurn:sha1:da9aa1f7f802552b9de459f331a2f39c84898009threadpool: 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
threadpool: lock mutex in create2020-02-12T21:05:28Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2020-02-12T14:00:16Zurn:sha1:09c8111c53a5adf3ca0e3d28d2b2652cc794efdb
In some contrived case, it might theoretically be the case that
destroy is called from another thread, which would modify the
threads array from two threads.
Coverity 208372
Merge pull request #61412020-01-17T01:45:44ZAlexander Blairsnipa@jagtech.io2020-01-17T01:45:43Zurn:sha1:c39ea485a043a234001dcd02e296331ea52554be
b9b5c473 threadpool: use std::move when taking an element off the queue (moneromooo-monero)
threadpool: use std::move when taking an element off the queue2019-11-15T13:24:34Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-11-12T18:38:38Zurn:sha1:b9b5c473d165c4ed59d012a9cd8e4c96dc546b74
It has a std::function, which can have a capture context, and
the function runtime might be small
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:1f2930ce0bec07e28958c059444151ad4968e1e6Removed a lot of unnecessary includes2018-11-15T16:29:34ZMartijn Ottogit@martijnotto.nl2018-11-15T16:29:34Zurn:sha1:bd98e99c8095cf05c4d3282c888a87745ad1c559Catch more exceptions in dtors2018-10-02T17:28:44Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-10-02T08:39:47Zurn:sha1:e5108a294a7d4fd923665e059a6eb90b0ab5a337
Misc coverity reports