Crash message: --- Krita has encountered an internal error: SAFE ASSERT (krita): "!m_d->staticCacheValid" in file /home/appimage/workspace/Krita_Stable_Appimage_Build/krita/libs/image/kis_transform_mask.cpp, line 431 Please report a bug to developers! Press Ignore to try to continue. Press Abort to see developers information (all unsaved data will be lost) --- STEPS TO REPRODUCE 1. Cloned ~10 layers of one source layer (no clones of clones) 2. Wrapped them in different groups 3. Applied transform masks to those groups 4. Did a "select opaque" 5. Painted a few strokes OBSERVED RESULT Crash EXPECTED RESULT No crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 18.04 KDE Plasma Version: 5.12.7 KDE Frameworks Version: 5.47.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION git hash: 15583ef
I'm sorry, but I haven't been able to reproduce the issue, at least not with the latest nightly build, though there haven't been any changes to kis_transform_mask.cpp since 4.1.5.
There has been changes now. @Larpon could you please check if it happens in the latest Krita (4.3.0)? I couldn't reproduce it - it takes some time updating, but works just fine. Since I cannot reproduce it, there is no backtrace and the assert is too generic to be useful, and there were changes to this part of the code, I don't think there is anything that we can use to fix the bug. I'm gonna change it to NeedsInfo so it will close automatically if there is no new information. If you still experience this crash and can reproduce it, please say so and maybe try to get the backtrace too - https://docs.krita.org/en/reference_manual/sharing_krita_logs.html#crash-log-and-backtrace
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
I haven't encountered this with 4.3.0 yet. I think this can be closed