<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Radar zoom GPU hang - desktop website v51.0.1]]></title><description><![CDATA[<p dir="auto">Zooming the map while the weather radar layer is playing back reliably crashes GPU rendering on the desktop website.</p>
<p dir="auto"><strong>Setup</strong>: <a href="http://windy.com" rel="nofollow ugc">windy.com</a> v51.0.1 on desktop Linux/NixOS - Brave 150.1.92.144 (Chromium), Mesa 26.1.5 (Intel iris driver), kernel 7.1.4-zen1, Intel Raptor Lake iGPU (i9-13980HX)</p>
<p dir="auto"><strong>Steps to reproduce</strong>:</p>
<p dir="auto">Open the map with the weather radar layer<br />
Pan around and zoom in/out for a while</p>
<p dir="auto">Within a minute or so I get a GPU hang. The OS kernel logs the hang against the browser's GPU process each time (GPU HANG … in brave from the i915 driver), rendering stalls for ~30 seconds, then the browser GPU process is killed and restarts. I also reproduced it on the previous kernel and Mesa versions too which I tried rolling back to. This also occurs for me in chrome which is version 150.0.7871.186.</p>
<p dir="auto">I saw this topic may be a similar or same issue?<br />
<a href="https://community.windy.com/topic/44064/map-crashes-when-zooming-radar-during-playback">https://community.windy.com/topic/44064/map-crashes-when-zooming-radar-during-playback</a></p>
]]></description><link>https://community.windy.com/topic/45153/radar-zoom-gpu-hang-desktop-website-v51.0.1</link><generator>RSS for Node</generator><lastBuildDate>Thu, 10 Sep 2026 23:03:51 GMT</lastBuildDate><atom:link href="https://community.windy.com/topic/45153.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 29 Jul 2026 10:49:59 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Radar zoom GPU hang - desktop website v51.0.1 on Thu, 30 Jul 2026 02:21:45 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/suty" aria-label="Profile: Suty">@<bdi>Suty</bdi></a> Thank you. Sorry I didn't see that thread earlier but yeah that looks like the same issue.</p>
<p dir="auto">Let me know if there is any logs or other info I can provide. I use NixOS and am happy to try other drivers or settings if there is anything that would be of help.</p>
<p dir="auto">Something I didn't mention in my report which may be useful toward debugging and fixing this...<br />
Originally the hang would result in my whole machine freezing into an unrecoverable state because the iGPU couldn't reset.<br />
Setting i915.enable_guc=2 means this only resulted in a 30 second freeze like I mentioned in the report rather than needing a complete restart of the laptop.<br />
This may just be peculiar to my system however, not sure but may be useful if you are having trouble working on this issue.</p>
<p dir="auto">Look forward to the new layers!</p>
]]></description><link>https://community.windy.com/post/230378</link><guid isPermaLink="true">https://community.windy.com/post/230378</guid><dc:creator><![CDATA[Cru Scanlan]]></dc:creator><pubDate>Thu, 30 Jul 2026 02:21:45 GMT</pubDate></item><item><title><![CDATA[Reply to Radar zoom GPU hang - desktop website v51.0.1 on Wed, 29 Jul 2026 12:39:54 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/cru-scanlan" aria-label="Profile: Cru-Scanlan">@<bdi>Cru-Scanlan</bdi></a> Hello there and thank you for reporting this. We are afraid that your issue is related to the one, our colleague describes <a href="https://community.windy.com/post/213242">here</a>.</p>
<p dir="auto">However, we are planning to release a new update of RadSat layers, so this should be improved there.</p>
]]></description><link>https://community.windy.com/post/230356</link><guid isPermaLink="true">https://community.windy.com/post/230356</guid><dc:creator><![CDATA[Suty]]></dc:creator><pubDate>Wed, 29 Jul 2026 12:39:54 GMT</pubDate></item></channel></rss>