KoboldCPP.exe v1.104 SDUI running Z Image Turbo unable to generate image, errors and exits program.

[alan-l]

Describe the Issue
A clear and detailed description of what the issue is, and how to duplicate it (if applicable).

Additional Information:
Please provide as much relevant information about your setup as possible, such as the Operating System, CPU, GPU, KoboldCpp Version, and relevant logs (helpful to include the launch params from the terminal output, flags and crash logs)
KoboldCPP.exe v1.104 running Z Image Turbo generates the following error:

Generating Image (9 steps)
ggml/src/ggml-vulkan/ggml-vulkan.cpp:5932: GGML_ASSERT(wg0 <= ctx->device->properties.limits.maxComputeWorkGroupCount[0] && wg1 <= ctx->device->properties.limits.maxComputeWorkGroupCount[1] && wg2 <= ctx->device->properties.limits.maxComputeWorkGroupCount[2]) failed

Going back to KoboldCPP.exe v1.103 generated image successfully.

Running on Intel Iris Xe with Vulkan.

[LostRuins]

Please try this version https://github.com/LostRuins/koboldcpp/actions/runs/20405966350/artifacts/4935735871

[JohnLoveJoy]

I tested it on my Vega (iGPU) and RDNA3 (dGPU) systems using Vulkan, and both work on the latest version, 1.104. It even seems a little faster.

What I noticed that doesn't work is Ovis 7B, unlike SD.cpp which does work. Weird.

[LostRuins]

Yeah i missed out adding OVIS. if it works ill add it next version

[alan-l]

Please try this version https://github.com/LostRuins/koboldcpp/actions/runs/20405966350/artifacts/4935735871

This one works on my Iris Xe, the prompt and settings I posted in CLBlast discussions is what I used. Is this version supposed to throw a bunch of GGML_ASSERT_CONTINUE outputs?

GGML_ASSERT_CONTINUE: ggml/src/ggml-vulkan/ggml-vulkan.cpp:5932: wg0 <= ctx->device->properties.limits.maxComputeWorkGroupCount[0] && wg1 <= ctx->device->properties.limits.maxComputeWorkGroupCount[1] && wg2 <= ctx->device->properties.limits.maxComputeWorkGroupCount[2]

I get about a dozen or so of the above output for each step generation. Each step generation takes about 36-38 seconds.

[GreenShadows]

Yeah i missed out adding OVIS. if it works ill add it next version

Great. I think the "Cancel All" button to stop image generation in the SD UI doesn't work either. Has anyone else noticed this?

[LostRuins]

@alan-l correct, it's actually overflowing one of the workgroups but i prevented that from halting the program.

@GreenShadows Cancel All doesn't stop in-progress generation, but it will clear the queue. Meaning if you queued 5 images and was halfway on image 2, it would clear 3,4, and 5, but still needs to complete 2.