Firefox Slow for Large Canvas Sizes about openoutpaint HOT 6 OPEN

while messing with chrome last night i actually noticed it recommending the willReadFrequently attribute on the contexts? i haven't tried it yet, i actually did a simple find and replace earlier to add it in to all contexts but then quickly realized that was a terrible idea while working on issue 90 and undid it lmao

https://html.spec.whatwg.org/multipage/canvas.html#concept-canvas-will-read-frequently
https://developer.mozilla.org/en-US/docs/Web/API/HTMLCanvasElement/getContext#parameters

basically just posting this so i don't lose the link again, not sure it'll be useful at all but hey, Thing That Improves Efficiency

from openoutpaint.

We actually do have some contexts using willreadfrequently, mainly some of the temporary color brush canvases, as they are used quite a lot for the cropCanvas function.

But it is indeed a very bad idea to use this for all contexts, as it basically disables hardware acceleration.

from openoutpaint.

welp testing the 10k x 10k output uhhh yep i can definitely confirm sketching on an absurdly large canvas in firefox is unpleasant lol - seems to be exacerbated by larger brush sizes?

from openoutpaint.

I'm not 100% sure this is related but I'm finding even smaller canvases, with firefox it just gets slower and slower and slower the longer you are working. I've noticed iteration time on generations rise higher and higher to the point that a generation that would take seconds a few hours ago now will take hours to complete.
Then I found if I changed the webui tab (I'm using this in a1111) to a different tab other than openOutpaint, bam the generation kicks up to normal speed again until you go back to the openOutpaint tab and then it will slow down again.

from openoutpaint.

i sheepishly admit i suspect most people are using openOutpaint for longer periods than i generally do; i blame ADHD? i can't say i've noticed that specifically myself but i also generally ricochet between tabs pretty often; i wonder however if you're running into something like this issue? also mentioned in the wiki but yeah, not really sure what to do with that one as i'll experience it just in webUI directly sometimes...

from openoutpaint.

The bit in the wiki seems pretty descriptive. That said, I will point out that so far I have only experienced this in openOutpaint, not A1111 itself. And then only in Firefox. In Brave browser (chromium) I haven't seen this issue (though in Brave, the "send to outpaint" doesn't work so I still tend to use Firefox)

It really feels to me like something about openOutpaint is, specifically in Firefox, causing performance issues the longer you use it which causes the GPU to be unavailable fully for generation.

But I'm no expert in this, only relating my observations.

from openoutpaint.