fredizzimo

Can you also provide a neovide log file, that should show what kind of window sizes are drawn. I suspect that if you have some scaling enabled, then it might...

I did a bit of digging and the macMini 2018 does indeed have problems with the memory and high resolutions, not just in Neovide, but everywhere https://forums.macrumors.com/threads/mac-mini-2018-bad-ui-performance-with-lg-5k-display.2154518/ That said there...

I will do some memory tracking on Windows, where I know the tools to do so, and have it booted up. The GPU memory usage does seem a bit excessive...

Can you try again with Neovide 0.11.0. A lot of things changed there.

Does [Alacritty](https://github.com/alacritty/alacritty), which uses the same winit library as we use for the windowing work?

This was closed before a proper solution was found https://github.com/ianyh/Amethyst/issues/1298. I suggest that you open a new issue there, I bet the Amethyst team has a much better chance of...

I'm not sure if the issue should be closed or not, on one hand @Ajibaji reports that it's working, while on the other hand @gennaro-tedesco reports that it doesn't.

I suggest that you create a new issue in the Amethyst repository for this. As I said earlier, they have a much better chance of figuring out what's wrong if...

Also, if it is a Neovide bug, one likely cause is the forking behaviour, so could you check with `neovide --no-fork`. BTW, that's a default behaviour I and many others...

I think the new winit update that we just merged in https://github.com/neovide/neovide/pull/1789 might have fixed the problem. Could you try again with Neovide master?