Exporting/saving (partially) freezes the app when using extended display

Is something not working like it should? Let us know.
User avatar

2021-11-03 15:42:34

Specs: MacBook Air M1, macOS Monterey, Pixelmator Pro 2.2 Carmel

Hi guys. Whenever I try to export my Pixelmator file (either by going File > Export or through Cmd + E) I get nothing in response and que tab becomes somewhat unresponsive. E.g. I can't close the tab with Cmd + W and even clicking the x button won't close it. Many other shortcut and actions become unresponsive as well.

EDIT:
Found out that it only happens while I'm using an extended display. More Information below.
User avatar

2021-11-04 11:35:04

Hi decosantee. Sorry to hear you're having trouble with Pixelmator Pro. If you're able to reproduce the hang consistently, could you collect a spindump log of the event and share it with us at support@pixelmator.com? We'll dig deeper into what's going on here.
User avatar

2021-11-04 11:38:45

The reproduction of the issue is definitely consistent. I’ll do that, thank you!
User avatar

2021-11-04 13:17:19

It started after I updated macOS to Monterey, so I suppose it messed with something UI related, I don't know. Just thought I should let you guys know.

EDIT:

I've noticed that this happens mainly when I'm working on an external/extended display.
User avatar

2021-11-08 13:56:22

by decosantee 2021-11-04 11:17:19 Ok, so I was messing with the settings of the app and after I switched Appearance from Dark mode to Light mode, as odd as it may seem, everything seemed to be working again. Exporting no longer makes the app unresponsive.

That's pretty much all I did. It started after I updated macOS to Monterey, so I suppose it messed with something UI related, I don't know. Just though I should let you guys know.

EDIT:

I've noticed that this happens mainly when I'm working on an external/extended display.
Thanks for sharing the report and the extra details. Our team's looking into this. I'll let you as soon as we know more. :pray:
User avatar

2021-11-08 21:28:01

i have this same issue, down to the detail about using an external display. if you need more reports, please just let me know and i'll try.
User avatar

2021-11-08 22:03:12

Ok here's another finding.

The following setup presents the issue I described:

Image

The following setups DO NOT present the issue:

Image
Image
User avatar

2021-11-08 23:01:22

per @decosantee my setup is the same. that's some great testing right there!

Image
User avatar

2021-11-10 01:14:07

Getting the exact same issue here on my M1 with an external display.
Disconnecting the external display or changing the relative screen positions does fix the issue...
User avatar

2021-11-11 13:18:33

Just a quick update: we've been testing this setup on macOS 12.1 beta and could no longer reproduce the issue there. For now, it seems we can expect a fix to be included in the next macOS update but do let us know in case the issue persists. In the meantime, thanks for providing us with a workaround, decosantee!
User avatar

2022-01-19 02:45:55

by Aurelija 2021-11-11 02:18:33 Just a quick update: we've been testing this setup on macOS 12.1 beta and could no longer reproduce the issue there. For now, it seems we can expect a fix to be included in the next macOS update but do let us know in case the issue persists. In the meantime, thanks for providing us with a workaround, decosantee!
Still experiencing the issue in MacOS 12.0.1

I had the same set up and the workaround worked seamlessly - such a random solution to un-stick it thank you.
User avatar

2022-01-21 14:14:56

by Luke M 2022-01-19 00:45:55
Still experiencing the issue in MacOS 12.0.1

I had the same set up and the workaround worked seamlessly - such a random solution to un-stick it thank you.
Just to be sure, are you running macOS 12.0.1 or macOS 12.1? These are two different versions and the issue seems to be fixed on macOS 12.1.