Walletwasabi: Wasabi GUI corrupted after minimizing/restore

[garceri]

General Description

Using Windows 10,sometimes Wasabi GUI becomes unusable (see screen below) after minimizing and restoring the window, this did not happen prior to 1.1.11
I keep wasabi minimized to avoid it from hogging my GPU and consuming power.

How To Reproduce?

1. Open wasabi
2. Open wallet and select the coinjoin or send tabs
3. minimize the window
4. After a while try to restore Wasabi window (seems to happen after a while not 100% of the time)
5. Gui is corrupted, but everything seems to continue working in the background,, you can click on the three menu items that get displayed and get the pull down menus, you can close Wasabi with Alt-F4.
6. See error

Screenshots

If applicable, add screenshots to help explain your problem.

Operating System

Windows 10 1909 x86_64 / Intel UHD 620 Graphics

Logs

There are no errors in the log whatsoever, everything looks normal.

Wasabi Version

1.1.11.0

[MaxHillebrand]

@danwalmsley @jmacato could you checkout 1] what this window size issue is [dan you did some changes here] and 2] why wasabi is so GUI hungry [there are several issues on this, it's odd]...

[garceri]

@jmacato @danwalmsley the GPU is used if you leave the window open in the Send or CoinJoin Tabs, if that rings a bell.
IMHO The GPU should not even be used, unless there is a good reason to do it, you are basically displaying text only, can we just disable HW Acceleration in Avalonia ?

[garceri]

I was able to recover the GUI by Selecting File|Lock Screen from the menu showing up at the center of the screen and then unlocking wasabi

[molnard]

I can reproduce this! My window was minimized for about 5 minutes while syncing the full node.
win10

I recovered by clicking on the Wallet Manager on the main menu.

[danwalmsley]

Syncing full node does that mean syncing filters or running your own node?

[garceri]

@molnard @danwalmsley in my case happens all the time while leaving running wasabi in the background, not when syncing filters, sometimes you reactivate it and the screen is corrupted..

[MaxHillebrand]

Syncing full node does that mean syncing filters or running your own node?

It means that your own local full node does not have all blocks verified, so the full node is still syncing.

[molnard]

Sorry for the confusion, syncing has nothing to do with the error. I meant there were some operations in the background that update the UI while minimized. If you delete the filters on client-side and start wasabi you will have similar behavior.

[jmacato]

Related error (basically different origins but same result as this one due to some garbage value getting into the render cycle that crashes it) https://github.com/AvaloniaUI/Avalonia/issues/3653

[danwalmsley]

Iv come across other ways this can happen... it is actually possible for drawing contexts to be passed nan or infinity and it will completely blank your screen... this could be case here, and needs fixing in Avalonia,,, at least so its not a silent failure.

There is also a Window blank after minimised issue open on avalonia too.

[danwalmsley]

https://github.com/AvaloniaUI/Avalonia/pull/3900

im adding this validation and warnings to avalonias render calls. This would allow us to detect and debug this kind of failure in the future.