On Tue, Apr 28, 2026 at 08:24:12PM +0200, Amin Shayan wrote: > Hi, > I have seen this crash in production for several days with the official > dockerized version 3.2.10, also upgraded to 3.2.16 with the same result. > After analysing a few coredumps and applying the following small patch, it has > been running in production so far without crashing.
Thanks for contacting us. The same issue was already reported to us yesterday on github. At first, we thought about applying the same patch as yours. However, this reveals longer term issues with the current task_schedule() implementation and its usage. Hopefully, the final solution should be found today or in the following days. In the meantime, you can revert the following commit (3.2 hash) : b9a39da6c36ef51a010300735d7b55a7cc67ee97 BUG/MEDIUM: tasks: Make sure we don't schedule a task already running Regards, -- Amaury Denoyelle
