Windy hangs up browser after loading
-
Windy is causing my browser hang after a part load. I have to kill the browser to get out of the program I am using Firefox on Mint Linux 22 and also doing the same thing on a Zorin Linux with Firefox. Need to be able to see the info on tropical storm that is coming at us in the Atlanta area.
-
@bobcheek16 Do you have issue only with specific layer in our app or where exactly?
-
I see the same issue with firefox and chrome based browsers on Linux Pop_OS. The browser will invariable freeze for several minutes when changing zoom level or swapping layers. There have been times when I've even had to kill the browser.
-
@stwepm HI there, unfortunately, we are not able to manage our app working on all open source versions of Linux. There can be some changes in their settings that can affect our app and its performance.
-
The same issue appears in Ubuntu24.04 (Ubuntu 24.04.2 LTS) in the latest Google Chrome browser (Version 135.0.7049.84 (Official Build) (64-bit))
My complete PC freezes when I am looking at the weather radar layer and using autoplay with goat speed. Usually I zoom around to see different regions.
Is it possible that there is a problem with how Windy.com interacts with the Nvidia GPU driver over Google Chrome browser?
Is there any setting that I can enable to make graphics more robust so that they would stop hanging the browser (and my PC)? -
@Matjaž-Škabar I have the same issue with firefox 138.0.4 (64-bit) on linus (nixOS) running wayland as window manager.
I don't have an external GPU (laptop with intel graphics), so it might be a webgl thing?It completly frooze my whole system twice after looking at the weather radar.
I'll try to reproduce with chromium and find some logs from the last crash. -
@landrae @Matjaž-Škabar Hi, WebGL is used in Windy to display some layers and if any addon or SW blocks this, the problem is made and Windy doesn't work without these.
-
Hi, I've ran into the same or very similar issue of a GPU hang on a Debian system with an integrated Intel GPU, both Firefox and Chrome, and after some searching I found that it is likely caused by a driver bug in the Mesa driver for Intel graphics. See this thread:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/11429
There is also a workaround mentioned in that thread, adding the line
INTEL_DEBUG=reemit
into/etc/environment
should help, but will likely also have some negative effect on performance.