# Protools setStateInfo + MML deadlock

**URL:** <https://forum.juce.com/t/protools-setstateinfo-mml-deadlock/20908>\
**Category:** General JUCE discussion\
**Created:** [February 10, 2017, 3:09pm UTC](https://forum.juce.com/t/protools-setstateinfo-mml-deadlock/20908 "2017-02-10T15:09:54Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![railjonrogut](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/railjonrogut/32/505_2.png) [@railjonrogut](https://forum.juce.com/u/railjonrogut)\
**Post date:** [February 10, 2017, 6:39pm UTC](https://forum.juce.com/t/protools-setstateinfo-mml-deadlock/20908/8 "2017-02-10T18:39:20Z")

</div>

> [@AaronLeese](#):
>
> suspect you could reproduce this by just adding MessageManagerLock mml (Thread::getCurrentThread())

You’ll find in AAX that Thread::getCurrentThread() returns NULL which is why it hangs… you probably need to use an AsyncUpdater. I have a separate Thread for loading my preset and I do something like that… but whatever you end up doing check it exhaustively on all platforms.

Your other option may be to set the AAX flag in the wrapper to load the chunk on the Message Thread.

Rail

---

_[View the full topic](https://forum.juce.com/t/protools-setstateinfo-mml-deadlock/20908)._