| Summary: | Safe assert in KisSelectionBasedImage when copying a Fill Layer | ||
|---|---|---|---|
| Product: | [Applications] krita | Reporter: | amyspark <amy> |
| Component: | Tools | Assignee: | Krita Bugs <krita-bugs-null> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | halla |
| Priority: | NOR | ||
| Version First Reported In: | git master (please specify the git hash!) | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Stacktraces of the two safe asserts | ||
|
Description
amyspark
2022-08-24 17:15:02 UTC
Confirmed (I built master with abort on safe asserts). Hm, I could only reproduce it once, though... Maybe there's a race trying to make the KisImageWSP a strongref somewhere? I can also get the assert when pasting, even if it didn't trigger when copying. Safe assert was introduced in https://invent.kde.org/graphics/krita/-/commit/250d243da6622af863c9b2090c452c292dd3d0fc , which was quite a long time ago... I don't know why it is triggering just now. There have been several changes in the way nodes are added to the layer stack, so maybe that's triggering something. Remove triaged keyword from CONFIRMED bugs |