Hi all, Since Threads.@spawn is encouraged over @async according to doc, so I decided to convert all @async to Threads.@spawn when reusing some of my old code. However, I’m getting some unexpected behaviors, for example when updating GLMakie figure. Here is a MWE where a figure is being updated …

Yes, I understand. As I said, it works for me with -t 4 or such. Check on which threads the respective tasks are running with Threads.threadid() during the loop. Maybe they migrate or something. @async schedules a task on the calling thread, i.e. in this case always on thread 1. function main() …

Unexpected behavior when using Threads.@spawn

General Usage

chiion September 5, 2023, 9:47am 8

Thank you, I think that’s the most likely explanation.

Guess I’ll have to use @async with any plotting related code for now just to be safe and make my own code to be thread safe for using Threads.@spawn

Topic		Replies	Views
Pluto - GLMakie Button action ok in @async but crashing with Threads.@spawn New to Julia pluto , glmakie	14	221	February 24, 2025
Hard crash using @spawn instead of @async New to Julia	7	322	April 1, 2024
Threads.@threads and Threads.@spawn General Usage parallel , multithreading	4	3621	November 26, 2019
Threads.@spawn not using master thread General Usage multithreading	2	800	November 24, 2019
@threads is really working in parallel? Julia at Scale multithreading	4	660	June 28, 2019

Unexpected behavior when using Threads.@spawn

Related topics