Bug 459459

Summary:	copy selection leads to crash
Product:	[Applications] krita	Reporter:	Manga Tengu <mangatengu>
Component:	* Unknown	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	amy, onecloud.shen
Priority:	NOR
Version:	5.1.1
Target Milestone:	---
Platform:	macOS (DMG)
OS:	macOS
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Manga Tengu 2022-09-20 20:00:51 UTC

I can't copy (cmd + c) a selection anymore. When I do so, I get the macOS color spinny wheel turning without stopping.
I'm not sure what causes this. Maybe an OS update ?

STEPS TO REPRODUCE
1. Make a rectangular selection
2. cmd + c

OBSERVED RESULT
Krita freezes and it's over (even the edit menu in the menu bar stays highlighted). If I was in the middle of a save, the popup still appears and the save still happens hopefully. If I switch app and try to switch back to krita, it won't show up. I have to get it with mission control at this point.

EXPECTED RESULT
I copy to my clipboard... and coffee appears in my cup.

MacOS 12.6

Comment 1 Manga Tengu 2022-09-20 21:52:21 UTC

I've done another copy and it worked. I don't know what made the difference. I'll try to come back with more info.

Comment 2 Manga Tengu 2022-09-21 10:44:15 UTC

It seems to happens on new files only.
So, this is what I think happened:
-I was drawing on a new canvas
-I fired a save
-while the file was still saving, I copied a selection and Krita froze
-the save success popup still appears but Krita was frozen to kill

Comment 3 Eewin 2022-09-22 18:52:36 UTC

This also happens to me. My platform is Windows 11, Krita version 5.1.1. I also tested on my Android pad, same issue happened. Looks like a bug for all platform.

The way to reproduce:
1. Open a new file
2. Create a selection mask layer (either global or local selection mask layer have the same issue)
3. Copy that selection mask layer
4. Paste layer, then Krita crash and exit

Comment 4 Manga Tengu 2022-09-23 06:11:46 UTC

In my case it already crashes at cmd C (copy)

Comment 5 amyspark 2022-09-26 16:45:39 UTC

This bug should be resolved as of the latest 5.1 nightly build.

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