# Is \`@async\` memory safe?

**URL:** <https://discourse.julialang.org/t/is-async-memory-safe/66558>\
**Category:** General Usage\
**Tags:** multithreading\
**Created:** [August 17, 2021, 3:37pm UTC](https://discourse.julialang.org/t/is-async-memory-safe/66558 "2021-08-17T15:37:05Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![ericphanson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ericphanson/32/215186_2.png) [@ericphanson](https://discourse.julialang.org/u/ericphanson)\
**Post date:** [August 18, 2021, 1:00am UTC](https://discourse.julialang.org/t/is-async-memory-safe/66558/5 "2021-08-18T01:00:54Z")

</div>

Xref

> [@Task scheduling semantics](https://discourse.julialang.org/t/task-scheduling-semantics/62950/2):
>
> I needed to know about the new behavior but was also confused about where to look. To link up some information I found: The co-scheduling behavior of @async tasks with their parent tasks was discussed in [https://github.com/JuliaLang/julia/issues/41324](https://github.com/JuliaLang/julia/issues/41324) For 1.7, it was decided that unsticky tasks become sticky if they launch any children with @async, thus ensuring that @async tasks always run on the same thread as their parent. [https://github.com/JuliaLang/julia/pull/41334](https://github.com/JuliaLang/julia/pull/41334) This probably isn’t…

---

_[View the full topic](https://discourse.julialang.org/t/is-async-memory-safe/66558)._