Bug 410777 - Merging a hidden group layer crash Krita
Summary: Merging a hidden group layer crash Krita
Status: RESOLVED DUPLICATE of bug 411124
Alias: None
Product: krita
Classification: Applications
Component: Layer Stack (show other bugs)
Version: 4.2.5
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-10 03:57 UTC by Khoo Hao Yit
Modified: 2019-08-30 13:22 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
kritacrash.log (234.78 KB, text/plain)
2019-08-10 03:57 UTC, Khoo Hao Yit 		Details
krita.log (155.79 KB, text/plain)
2019-08-10 10:34 UTC, Khoo Hao Yit 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Khoo Hao Yit 2019-08-10 03:57:46 UTC 
Created attachment 122043 [details]
kritacrash.log

SUMMARY
Merging a hidden layer crash Krita.

STEPS TO REPRODUCE
1. Have a paint layer inside a group layer.
2. Hide the group layer.
3. Click on the group layer and merge it (Ctrl + E).

OBSERVED RESULT
Freeze and crash.

EXPECTED RESULT
Merged layer.

SOFTWARE/OS VERSIONS
Windows: Microsoft Windows 10 Pro, Version 10.0.17763 Build 17763
Comment 1 Halla Rempt 2019-08-10 08:35:25 UTC 
I'm sorry, I cannot reproduce this issue. Are you sure you're using Krita 4.2.5? Could you also attach the krita.log file to the bug report?
Comment 2 Khoo Hao Yit 2019-08-10 10:34:57 UTC 
Created attachment 122045 [details]
krita.log
Comment 3 Khoo Hao Yit 2019-08-10 10:40:42 UTC 
The attachment has been upload. https://bugs.kde.org/attachment.cgi?id=122045
Comment 4 Halla Rempt 2019-08-11 10:46:35 UTC 
Does this only happen with Noel.kra, or does it happen with any image for you? If the former, could you share that with us so we could test with it?
Comment 5 Khoo Hao Yit 2019-08-11 11:18:27 UTC 
It works with any image for me.
https://youtu.be/BXOTfKMqV1U
Comment 6 Halla Rempt 2019-08-30 13:22:27 UTC 
I fixed this in the meantime :-)

*** This bug has been marked as a duplicate of bug 411124 ***