Expected & actual behavior
I have a dell precision with a 4k display. Because ubuntu doesn't let you use different scaling on my external 4k monitors, I keep the laptop display on 1080p. This doesn't happen until I log in- the resolution on the lock screen is still 4k.
Any time the resolution changes, if wavebox is open, it freezes. I can still move the window around, minimize it etc... but I cannot click or interact with anything in the window. The only way out is to use the blue tray icon to close the app and restart.
Steps to reproduce
It happens to me 100% of the time when changing the resolution on the monitor that wavebox is on.
Hello, If possible can you do 2 tests?

NOTE: Above image is from GIT and so it might look different then from what you have in stable.
Good call. Disabled hardware acceleration, issue went away. (Isolate Account Processes was also disabled by default).
I then installed the .deb, and replicated the behavior. Same thing though, disabling hardware acceleration gets it to work properly.
Do you know which GPU you have in your machine? I wonder if it's down to some incompatibility with that :-/
Dell Precision 5520
VGA: Intel Corporation HD Graphics P630 (rev 04)
3D: NVIDIA Corporation GM107GLM [Quadro M1200 Mobile]
(I had expected the nvidia one to come up for both- don't know if this means I misconfigured something!)
Thanks, I'll have a look to see if I can reproduce. We're working on bringing the beta channel of Wavebox to stable at the moment and this has a newer chromium version. There could be some fixes in there too for graphics related issues
@pbecotte we've just released a new version (v4.0.0) of Wavebox with a new version of Chromium that will hopefully fix this. It would be good to know if it has fixed it for you. Thanks
No, it actually was a bit worse (it was harder to kill it when it happened). Of course, it seems to run pretty well without the hardware acceleration...
Okay thanks! Good to know that HW acceleration fixes it in the meantime.
I'll pop the electron-3 label on this for now, there's quite a big version jump in terms of Chromium for that one and it should have better compatability.
Hi, I was just wondering if you've had a chance to try this with Version 4.5.0? It has an updated version of Chromium and we're hoping that this has fixed this issue. Thanks
Gave this a shot and it appears to have resolved the issue. Nice! Will close this for now and come back if I see anything else related to this issue.
Most helpful comment
Gave this a shot and it appears to have resolved the issue. Nice! Will close this for now and come back if I see anything else related to this issue.