comfyanonymous
The webui can be used for a period of time and then no response
Your question
The webUI can be used for a period of time and then no response. When I click the button 'Queue Prompt', the backend can print out message normally. Finally I find out that there's something wrong with the function 'publish_loop' in the Class 'PromptServer'. 'self.messages.put_nowait' can normally add item into the queue, but 'await self.messages.get()' is stuck and the msg can't be sent out by socket any more. How can I fix this Problem?
Logs
No response
Other
No response
Can you write down detailed reproduction steps? e.g. 1. Click ... 2. Click .. 3. Observe ...
Can you write down detailed reproduction steps? e.g. 1. Click ... 2. Click .. 3. Observe ...
There's no step. The webUI can run normally for a period of time. Maybe one hour, maybe two...But finally it will be no response. I find out that the code 'await self.messages.get()' is stuck, but I don't know why and how it happens?
By the way，I also run the webUI in the iframe on other website and there’s going to be a situation like multiple user. Is there any problem like that?
Hmmm, seems to be a hard to repro flaky issue. How did you managed to get down to await self.messages.get()?
Hmmm, seems to be a hard to repro flaky issue. How did you managed to get down to
await self.messages.get()?
when there’s no response on the webui, the http request works and the terminal prints out the logging info，so I realize that the problem is on the socket. Just step by step. post_prompt > prompt_queue.put > queue_updated > send_sync and finally 'await self.messages.get' in publish_loop is stuck
Fortunately，I finally find out that it's the custom nodes named Crystools which causes this problem. All I have to do is to disable it. Maybe it sends too many socket messages? I don't know the deep reason.
Hmmm. Maybe you can file an issue in the custom node repo instead. Closing this for now.
Fortunately，I finally find out that it's the custom nodes named Crystools which causes this problem. All I have to do is to disable it. Maybe it sends too many socket messages? I don't know the deep reason.
@crystian Maybe the resource monitor is causing this error.
Fortunately，I finally find out that it's the custom nodes named Crystools which causes this problem. All I have to do is to disable it. Maybe it sends too many socket messages? I don't know the deep reason.
please create an issue on my repo. I don't believe that raises only with my node (many people will be affected by it), but we'll check it! (fill the form please!)
