Direct2D: hitting assert when changing monitor resolution

[stephenk]

I am running JUCE 8.0.8 and hit an assert if the monitor resolution changes. This is inside a standalone GUI app. Windows 10.

I normally run my monitor at 150% and 3840 x 2160.

So I change the display to 2560 x 1440.

I then hit an assert in Direct2DPixelData::createPersistentBackup()

The call stack looks like this:

Should I be doing something so that this doesn’t happen?

[reuk]

If you continue execution after the assertion, does the program continue to function correctly?

[stephenk]

Hi reuk. I have to hit continue like 20 times, because I guess it keeps hitting for multiple onscreen components, but yes it does seem to recover and function correctly regardless. So perhaps the assert is not really needed.