# Is there any safe way to use ThreadPool::getJob()?

**URL:** <https://forum.juce.com/t/is-there-any-safe-way-to-use-threadpool-getjob/35946>\
**Category:** General JUCE discussion\
**Created:** [October 31, 2019, 2:51pm UTC](https://forum.juce.com/t/is-there-any-safe-way-to-use-threadpool-getjob/35946 "2019-10-31T14:51:29Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![RolandMR](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/rolandmr/32/641_2.png) [@RolandMR](https://forum.juce.com/u/RolandMR)\
**Post date:** [October 31, 2019, 2:51pm UTC](https://forum.juce.com/t/is-there-any-safe-way-to-use-threadpool-getjob/35946/1 "2019-10-31T14:51:29Z")

</div>

Is there any safe way to use `ThreadPool::getJob()`? Whatever gets returned can be deleted be the time I go to use it. Shouldn’t the `ThreadPool` expose its `CriticalSection`?