You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue exists on a clean installation of Fooocus
The issue exists in the current version of Fooocus
The issue has not been reported before recently
The issue has been reported before but has not been fixed yet
What happened?
It seems that there is an issue with task loss in the queue management within the code. While I had an ongoing task running, I triggered two different rendering tasks consecutively, each time setting async_process to true.
At that point, there were a total of three tasks queued for execution. However, after approximately 15 minutes, when I checked back, I noticed that the last task had never been executed — its start_mills value was null.
Steps to reproduce the problem
Start a task that is running.
Initiate two additional rendering tasks with async_process set to true.
Checklist
What happened?
It seems that there is an issue with task loss in the queue management within the code. While I had an ongoing task running, I triggered two different rendering tasks consecutively, each time setting
async_process
totrue
.At that point, there were a total of three tasks queued for execution. However, after approximately 15 minutes, when I checked back, I noticed that the last task had never been executed — its
start_mills
value wasnull
.Steps to reproduce the problem
async_process
set totrue
.What should have happened?
All task should be finished.
What browsers do you use to access Fooocus?
No response
Where are you running Fooocus?
Locally with virtualization (e.g. Docker)
What operating system are you using?
Linux
Console logs
Additional information
4090
The text was updated successfully, but these errors were encountered: