Hello @rendnarb,

This sounds like a bug that we've already discovered and fixed internally. An update with the fix should hopefully be live in a week or two.

In the meantime you can try the following:

• Long-press the Windy app on your phone.
• Select "App info", go to "Storage and cache".
• Press the "Clear storage" button.

This will clear most of your settings and log you out, however things such as your favourites are stored in the cloud and will be available after you log back in.

Do not enable the following features in your app before the next update is live:

• The Airports and VFR airspaces map
• Isolines
• The "Weather Warnings" layer
• The "Hurricane tracker" layer

The VFR airspaces map is the one we've discovered is causing the issues. The other listed features seem to work fine on the devices we have for testing, but it is possible that they could also trigger the crash, since they use the same rendering path as airspaces.

Please let me know if the issue persists after the update or if you try the workaround and it doesn't help. Thanks!

Hello!

Thank you for reporting this issue! Our current guess is that this only occurs on the PowerVR GPUs in your specific phone models. We're sourcing a comparable phone for debugging now, as the issue does not show up on any of our current testing phones.

Hello, we've found a fix, it'll go live in the next major version (50). I'll post here again once the fix is live.

Hi, the larger pattern is intentional, but we'll consider reverting it back to a smaller pattern in the next major update.

It does look like the pattern is somewhat larger than it should be in your screenshot. Can you please share what OS, screen resolution, browser and scaling settings (system display scaling, scaling in browser, font scaling, etc.) you are using?

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.

Hi, I second what @suty has said and I'll give a bit more detail. Your overrides block canvas readback, which we need to properly parse our data tiles. Your config worked in previous versions, because we used to do this via WebGL texture readback, but that method had poor performance. I'm afraid we won't be going back.

The problem seems to be your specific overrides, Windy works fine with just privacy.fingerprintingProtection = true on my system. Your best bet is finding a way to whitelist canvas readback for Windy in Firefox.

Hi, the larger pattern is intentional, but we'll consider reverting it back to a smaller pattern in the next major update.

It does look like the pattern is somewhat larger than it should be in your screenshot. Can you please share what OS, screen resolution, browser and scaling settings (system display scaling, scaling in browser, font scaling, etc.) you are using?

Hi, we know about this issue and it has been fixed in version 50, which released just yesterday for the web (apps will follow soon-ish). If you want to try it out, navigate to windy.com in a web browser on your phone.

Please let us know if you still see the particles issue in v50. Since it was caused by a driver bug, it is entirely possible that the issue is still present on some combination of hardware+software, even though works fine on phones we tested.

See this thread for more details:

https://community.windy.com/topic/43717/wind-animations/36

Hello, version 50 has just released for the web. It should fix these particle issues.

Note that the mobile apps are still on version 49, they will be updated in the near future. You can use the new version of windy.com on your phones using a web browser (Chrome/Firefox, etc.).

Please let us know if you see broken particles animation on the new version. It works on the devices we have for testing, but since it was caused by a driver bug, it is always possible that some combination of hardware+software still has the issue.

Hi, since you have a somewhat recent Intel GPU (newer than Sandy Bridge), then this is likely caused by a driver bug in Mesa. Please see this post for a workaround:

https://community.windy.com/post/213242

You could also try configuring your browser to use the Nvidia GPU instead. But this would probably cause your notebook to drain its battery a bit faster when using the browser.

Hi, if you have a somewhat recent Intel GPU (newer than Sandy Bridge), then this is likely caused by a driver bug in Mesa. Please see this post for a workaround:

https://community.windy.com/post/213242

Hi, I second what @suty has said and I'll give a bit more detail. Your overrides block canvas readback, which we need to properly parse our data tiles. Your config worked in previous versions, because we used to do this via WebGL texture readback, but that method had poor performance. I'm afraid we won't be going back.

The problem seems to be your specific overrides, Windy works fine with just privacy.fingerprintingProtection = true on my system. Your best bet is finding a way to whitelist canvas readback for Windy in Firefox.

Hello, we've found a fix, it'll go live in the next major version (50). I'll post here again once the fix is live.

Hello!

Thank you for reporting this issue! Our current guess is that this only occurs on the PowerVR GPUs in your specific phone models. We're sourcing a comparable phone for debugging now, as the issue does not show up on any of our current testing phones.

Hello @rendnarb,

This sounds like a bug that we've already discovered and fixed internally. An update with the fix should hopefully be live in a week or two.

In the meantime you can try the following:

• Long-press the Windy app on your phone.
• Select "App info", go to "Storage and cache".
• Press the "Clear storage" button.

This will clear most of your settings and log you out, however things such as your favourites are stored in the cloud and will be available after you log back in.

Do not enable the following features in your app before the next update is live:

• The Airports and VFR airspaces map
• Isolines
• The "Weather Warnings" layer
• The "Hurricane tracker" layer

The VFR airspaces map is the one we've discovered is causing the issues. The other listed features seem to work fine on the devices we have for testing, but it is possible that they could also trigger the crash, since they use the same rendering path as airspaces.

Please let me know if the issue persists after the update or if you try the workaround and it doesn't help. Thanks!

Hi @gambirch

The double tap + hold zoom gesture should work on all layers in the new beta version, feel free to try it out! Though the beta is currently only out for web browsers, not mobile apps.