# Slicer crashes when using QThreadPool to start QRunnable in python module

**URL:** <https://discourse.slicer.org/t/slicer-crashes-when-using-qthreadpool-to-start-qrunnable-in-python-module/8596>\
**Category:** Support\
**Created:** [September 27, 2019, 10:17pm UTC](https://discourse.slicer.org/t/slicer-crashes-when-using-qthreadpool-to-start-qrunnable-in-python-module/8596 "2019-09-27T22:17:56Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![jamesobutler](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jamesobutler/32/7511_2.png) [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)\
**Post date:** [September 30, 2019, 6:51pm UTC](https://discourse.slicer.org/t/slicer-crashes-when-using-qthreadpool-to-start-qrunnable-in-python-module/8596/12 "2019-09-30T18:51:48Z")

</div>

> [@lassoan](#):
>
> Currently, Slicer’s scheduler runs Python CLIs one by one, but it would be possible to change this

We previously had a discussion ([Running multiple CLIs at once](https://discourse.slicer.org/t/running-multiple-clis-at-once/7686)) about this, but didn’t take any action yet.

---

_[View the full topic](https://discourse.slicer.org/t/slicer-crashes-when-using-qthreadpool-to-start-qrunnable-in-python-module/8596)._