Clock example freezes after monitor goes into standby (Win10)

Is there an existing issue for this?

• I have searched the existing issues.

Is this issue related to iced?

• My hardware is compatible and my graphics drivers are up-to-date.

What happened?

Hi there!

Today, I started the the clock example and let it run for a while. During that time, my computer monitor was put into standby (after 20 minutes). After that, I "woke up" my computer monitor by simply moving the mouse. The clock example was still visible, but it seemed to be not running anymore and was frozen in time. At first, I thought the example might have thrown an exception, but it didn't.

To further investigate, I found out that every time when my computer monitor was put into sleep mode by Windows 10, every iced app that I have tested had stopped redrawing the gui.

If I click somewhere or type a few keys on my keyboard, the gui is "unfrozen" again.

It might not even have something to do with the iced library itself since it only happens, after my computer monitor was put into standby mode, but could rather be a problem with winit / wgpu.

Can anybody of you reproduce this?

It is a bit tedious, since we'd have to wait until Windows 10 puts the display into sleep mode, but this is exactly, what triggers the issue.

What is the expected behavior?

Nothing should be frozen in time.

Version

master

Operative System

Windows

Do you have any log output?

Sadly, since nothing crashed but rather was not "redrawn", there is no log output :(