Ongoing Interface/generation that freezes machines.

### Custom Node Testing

- [x] I have tried disabling custom nodes and the issue persists (see [how to disable custom nodes](https://docs.comfy.org/troubleshooting/custom-node-issues#step-1%3A-test-with-all-custom-nodes-disabled) if you need help)

### Expected Behavior

This is a continuation of the previous closed thread that I believe warrants actual attention.

https://github.com/Comfy-Org/ComfyUI/issues/9583

So mine will freeze with zimage turbo gens on ksmapler, sometimes other nodes, but 90% ksampler.

For weeks I looked and tried solutions and nothing worked. What did work is stupid...

minimized comfyui desktop or in browser i switched to a different tab and within seconds it began working.

Taking a further look at system resources through recording I noticed random millisecond GPU spikes during the initial stages of generation, but the GPU spikes came from ComfyUI interface itself and not my powerful machine (4090, 64gb ram), which further supports that the UI is doing something at the same time as the image gen process, that depending on millisecond timing will block and continue to block generation freezing the entire machine.

Whatever comfyui is doing at the start will sometimes bottle neck and freeze during the initial stages of the gen.

I hope this is helpful to find a proper solution.

### Actual Behavior

GPU spikes during initial image generation from the comfyui gui where its looks like loading of models gets jammed.

only noticeable with z-image turbo generations so far.

### Steps to Reproduce

standard work flow.

z-image turbo.

generic settings.

freeze during initial image gen and system freeze, often ksampler or clip text encode.

doesn't happen every time, changing settings before gen or during gen may induce but not always.

but once it does happen, you need to or minimize comfyui app/browser tab for it to work.

only restarting will refresh whats seems to be still blocking it.

### Debug Logs

```powershell
- at request. - so far the logs show normal activity unfortunately, comparing successful generation and frozen generation.
```

### Other

_No response_

Start by reproducing the standard z-image turbo workflow, focusing on KSampler and CLIP text encode during the initial generation stage. Compare successful and frozen runs through the available debug logs and system-resource recording; done means identifying a reliable cause and a reproducible fix for the interface-related freeze.

Written by the indexing model from the issue text.