[BUG] Forge Failed with HIRES input image on Generate Forever

Nobody has claimed this yet.

I'm using version f2.0.1v1.10.1-v1.6.0 of Forge, Windows 10 22H2 on AMD Ryzen with 64 RAM, RTX 3060 12GB VRAM and video driver 551.61. I gave him on img2img with SDXL model a picture of the resolution 4096x4096 with Ultimate SD Upscale script for tiled repainting and Forge somehow failed after the first generation.

In console he continued to generate and to save pictures, he updated preview window with the generated image but only once, in WEBUI progress bar collapsed (just standing on "Waiting") and orange button Generate started to flashing between Generate button and grey buttons Interrupt/Skip. Automatic1111 was able to hold on for 12 hours of generations with hires pictures, but he is much slower than Forge and without Flux support.

I tried in Settings to turn off Live Preview and "Show progressbar" but Forge continued with flashing in the browser TAB name, between "Stable Diffusion" and percentage of done until he stooped after some time. And very soon after, maybe after 6-10 pictures, WEBUI disappeared and the console stopped with generating (in Vivaldi browser).

The same thing happened but a little slower during the operation of upscaling from 1024 to 2048 in img2img with SDXL and Ultimate SD Upscale script and ControlNet lineart used, somewhere in between 20-30 generated images and solution is to restart Forge and relaunch WEBUI only to watch it happen again.

It seems to me that the connection with the server is somehow lost, I noticed that it also happened after I minimized the browser with WEBUI and when I started a movie to check or when I was doing something with images in Photoshop, as if it was a trigger. But Forge never uses VRAM more than half and only for a short time when it completes the image it jumps into RAM. Will be great if you can make Forge great again, thank you.

Start by reproducing the failure through img2img with an SDXL model, Ultimate SD Upscale, and the described 4096x4096 or 1024-to-2048 workflow, while observing the console and browser UI. Compare behavior with Generate Forever, ControlNet lineart, minimized-browser use, and the listed Windows environment. Done means the failure condition is isolated and a reliable fix or regression check prevents the UI and generation process from stopping.

Written by the indexing model from the issue text.