[bug]: After using brush (letting go of mouse button) on canvas, there's always some stutter/freeze/lag

[mcbexx]

Is there an existing issue for this problem?

• I have searched the existing issues

Operating system

Windows

GPU vendor

Nvidia (CUDA)

GPU model

2070 Super

GPU VRAM

8

Version number

5.6.0

Browser

Firefox 134.0.2

Python dependencies

No response

What happened

Whenever I use a brush in canvas mode, be it on an inpaint mask layer or a raster layer, the mouse cursor very briefly stutters/freezes after letting go of the mouse button, which makes quick successive brushstrokes basically impossible.

This happens regardless of brush size or the number/complexity of layers on the canvas - a single raster and inpaint layer already causes the freezes.
I wanna say this has been an issue since the introduction of v5.0, it definetely did not occur before (long time user).

I am assuming this is a local issue, since this impeding behaviour would have come up before otherwise.

What you expected to happen

I expected no freezes when letting go of the mouse button

How to reproduce the problem

No response

Additional context

AMD 3900x CPU, 32 GB RAM, RTX 2070 Super, GeForce driver 566.36 (Dec 5, 2024).

Discord username

No response

[mcbexx]

Edit: It appears that switching from the Web UI to the "Window App" mode seems to fix the stutters (although I assume the App is just a wrapper for the web interface?)

[psychedelicious]

Yeah, it's just running the web interface in an electron window, which is a stripped down build of the Chrome web browser.

Things to try to narrow down the cause:

• Disable all extensions (some extensions to terrible things to site performance, for example 1Password likes to inject itself into every form element and can really bog things down)
• Private window
• Different browser (e.g. Edge)

FWIW, Chromium/V8 is much faster than FF for many HTML Canvas operations. One reason we made the launcher in electron is to ensure all users have the most performant UI across all platforms. That said I use FF locally on macOS and can't say I've run into this issue.