Error on undo: 'LayerManager' object has no attribute 'active' #862
Comments
|
I've been having a lot of trouble with it saying "' has no attribute 'Active'" since I updated it recently. I can do maybe 3 or 4 operations and get a few minutes of work done but then I try to bake the generation into the layer with the check mark and nothing happens, then it'll complain about that layer not having the active attribute. I can't figure out how to reproduce but to keep working and it just seems to happen randomly. IT doesn't go away unless I restart Krita, but often times Krita will just get tired of me trying to figure out what causes it and it crashes on me. Also, getting this Script Error: Will update here if I find anything, as it's the closest open issue that seems to be related, rather than making a new one. Edit: I notice a lot of Errors that are like ERROR:root:ERROR lora diffusion_model.input_blocks.8.1.transformer_blocks.0.attn2.to_k.weight shape '[1280, 768]' is invalid for input of size 2621440 in the console also. @arcusmaximus, are you getting any errors in comfyui's console? I'm using Stability Matrix to manage the Comfy server, that makes it easier to see server errors. |
|
|
I don't use Loras in the Styles, so this might be causing compatibility issues with the xenoxtcArtToonPortraitsAnd_vtoon model in Hyper mode. Will futz with it further, and see what I see. LayerManager Issue:
Bugged Behavior: Restarting live mode after this error causes Krita to lose the active layer, and the generated result is not placed. Steps to Reproduce: Flatten the image using Shift-Ctrl-E to create a root Merged layer. Krita might not be handling the layer removal correctly, especially when it's not done through Krita's own layer delete function. This issue could also be triggered by using the Flatten Image function itself, not sure. Consider adding a check to ensure a background layer is created if the active layer delete problem happens and also make sure that if it can't create the result layer, that it won't, much like the create new layer from result does, that check option just doesn't make a layer when it's bugged out. This might prevent the project from breaking and help identify other causes where the active layer gets lost. But this is all a pretty unusual use case, I only found it by trying anything I could think of to reproduce the behavior. Maybe it helps? Hopefully whatever causes it for others can be helped either with some catches. Best for user to a;sp use the script's result to active layer/ new layer and not Flatten. I was doing flatten and merge by hand before the latest version so that probably helped find that. I won't have the issue now since I won't flatten but still, it may indicate weirdness in the script and Krita? Sorry, this is kind of a mess. I keep having to edit it after finding new things. There was an error reporting but it was actually photoshop in background trying to call the server so unrelated... hopefully this is of some value. |
|
It's possible there is an issue when there is only a single layer. Apply will create a new one and remove the old one, but even though the order is such that the new layer is created first, it briefly results in no layers / no active layer. I thought the fallback worked for that though, and I couldn't really reproduce the error. Still, best to avoid the situation by delaying deletion until after Krita had a chance to process creating the new layer. |
|
If you are still getting errors in 1.20.0 let me know and post check client.log for error message |
This one happened when pressing Undo after accidentally flattening the entire image. No ControlNet or regions active. Sadly can't reproduce.
The text was updated successfully, but these errors were encountered: