Affinity Designer 2.5.5 freezes after hibernation

[jcamachott]

I've noticed this several times now.

1. I run Designer on Windows 11 at location A.
2. I then minimize the app and continue working with other apps.
3. I hibernate the pc since I'm changing location to location B
4. At new location, computer comes out of hibernation.
5. When I restore Designer, it is either not responsive or if I try to do something in the UI, the app freezes and I get an opaque white screen.
6. I then have to force close the app.

This has happened half a dozen times already and I'm using the app just over a month.

Note that location A has a portable 15" external monitor I use via HDMI. Location B has a different external monitor, 28", also HDMI.

I can try to experiment with not using the external monitors at all and see if that makes a difference. 

Has anyone else experienced this?

[Pšenda]

5 hours ago, jcamachott said:

Has anyone else experienced this?

No, I use hibernation regularly and repeatedly, on desktop and laptop, but always without switching monitors.

[thomaso]

Hi @jcamachott, welcome to the Affinity forums!

7 hours ago, jcamachott said:

I then minimize the app and continue working with other apps.

• Is it different if you do not minimize the app?
• Do you save in Affinity before minimizing or sleep mode?

8 hours ago, jcamachott said:

the app freezes and I get an opaque white screen

A "white screen" issue seems to be Windows specific and does not occur on mac but possibly Affinity issues have common culprits, so just in case:

On an earlier Macbook (until ~2020) I often experienced different error messages (e.g. 'document corrupted' / 'could not read' / 'can not access') or app freezes, either when waking up from hibernation or when saving – but not while working in Affinity. The issue was independent of the use of the external monitor. I had not minimized the app before hibernation. Often I had not saved the open Affinity documents before the mac went to sleep (I trusted to Affinity's restore feature).

I never detected the cause of the problem. The Affinity errors seemed to occur less frequently when I saved more frequently and with a different file name / before sleep mode.

The affected Macbook had two internal hard drives: an SSD (operating system, applications, system user folder) and an HD (Affinity documents, resource/image files). External volumes were not used. I was wondering if the SSD + HD combination caused a problem, as it was also noticeable that working on documents went smoothly, but waking up from sleep mode or saving triggered the error, as if Affinity couldn't communicate between temporary files (.autosave, on SSD) and already saved versions (on HD) in time/fast enough. Perhaps such a delay caused the problems when waking from sleep?

[jcamachott]

On 11/2/2024 at 4:27 AM, Pšenda said:

No, I use hibernation regularly and repeatedly, on desktop and laptop, but always without switching monitors.

Yes, once I am connected to the same external monitor I can hibernate without an issue

[Callum]

Hi All, apologies for the delayed response.

@jcamachott is this something you are still having issues with? I have tried replicating this here at my end but haven't been able to even when switching displays after hibernation etc. Are you using a dock etc when switching locations?

Thanks
C

[jcamachott]

Hi

I have been closing my app just before hibernating. But I will test it during this week and let you know.

[jcamachott]

Hi @Callum So it happened again. Was working outside of home, using a 15" external monitor. Left Affinity Designer 2.5.7 open, hibernated, then when I got home and connected to the 28" monitor, at first when I opened the AD window, I was able to scroll around the document. Then I went into File > New and after clicking on the Create button, that's when I got the hourglass, and the app froze.

Had to end the task. What info you need from me to help you troubleshoot this?

Edited January 22 by jcamachott

[Callum]

Hi Jcamaschott,

Ideally we would need to be able to recreate this issue here in order to investigate the cause, please could you confirm if you are using any docks etc when switching displays or are you plugging directly into the monitor? I will likely need to get an opinion from our QA team in regards to where to look for potential clues for this issue I will speak to them tomorrow and hopefully have more info for you then.

[jcamachott]

Hi @Callum let me give you some more info.

I am on Windows 11, Lenovo LOQ, 12th gen i5, 32gb RAM. Nvidia GeForce RTX 3050

I connect to a 28 inch dell monitor at home. HDMI direct connection, no hub.

Outside of home I use a 15" portable monitor. HDMI direct connection, no hub.