I was recording some stuff with Krita 4 pre-alpha and I noticed very high CPU usage from both Krita & OBS, there's some weird interaction with the graphics card I think, cause I noticed this when I play youtube videos as well and keep them on my other monitor open. And I usually see this in the console. I have no idea what it means but it might be related? I haven't noticed these logs in Krita 3.1.4 and 3.1.4 seems pretty stable when running OBS & Youtube/other vids in comparison krita.core: BUG: The walker hasn't reached the root layer! krita.core: BUG: The walker hasn't reached the root layer! krita.core: Start node: KisPaintLayer(0x21c15160, name = "Layer 2") Requested rect: QRect(512,0 288x512) krita.core: There must be an inconsistency in the walkers happened! krita.core: Please report a bug describing how you got this message. krita.core: BUG: The walker hasn't reached the root layer! krita.core: Start node: KisPaintLayer(0x21c15160, name = "Layer 2") Requested rect: QRect(0,512 512x288) krita.core: There must be an inconsistency in the walkers happened! krita.core: Please report a bug describing how you got this message. krita.core: BUG: The walker hasn't reached the root layer! krita.core: Start node: KisPaintLayer(0x21c15160, name = "Layer 2") Requested rect: QRect(0,0 512x512) krita.core: There must be an inconsistency in the walkers happened! krita.core: Please report a bug describing how you got this message. krita.core: Start node: KisPaintLayer(0x21c15160, name = "Layer 2") Requested rect: QRect(512,512 288x288) krita.core: There must be an inconsistency in the walkers happened! krita.core: Please report a bug describing how you got this message. krita.lib.flake: the context stack is not empty (current count 1 , expected 0) libpng warning: iCCP: too many profiles SAFE ASSERT (krita): "m_d->lastKnownValue.isNull() || result == m_d->lastKnownValue" in file /krita-4.0.0-prealpha/libs/flake/KoDerivedResourceConverter.cpp, line 70 Could not lock the document for saving! Could not lock the document for saving! Could not lock the document for saving! Could not lock the document for saving!
I take it back... the spikes happen with Krita 3.1.4 as well :/
OK, I know it's highly likely that my CPU isn't strong enough to do this recording without these spikes, I just reported the bug cause I think the console log might be related somehow with these spikes... don't know.
Well, "Could not lock the document for saving!" -- that happens when Krita is still busy calculating the image. So, either your image is crazy large or crazy complex, or something is hogging the cpu. I'd look at top, and check available memory.
In the meantime, this is not a bug in Krita.