Critical Bug: Web version freezes/crashes when set to UTC time (Memory Leak)
-
Description: Since today, I've experienced severe freezing and browser crashes when using Windy.com on the web. The issue seems directly related to the UTC time setting.
Steps to Reproduce:
Open Windy.com.
Go to Settings and change "Display time" to UTC.
Search for an airport code (e.g., VHHH). It works initially.
Search for a second airport code or click the "Meteogram" icon.
The page becomes unresponsive. Memory usage (RAM) spikes rapidly from ~200MB to over 330MB+ within seconds.
Observations:
The issue persists even in Incognito mode if UTC is enabled.
If I stay on "Local Time," the crash occurs much less frequently.
This happens on both Windows 7 and the latest Windows/Chrome versions.
"Compare" and "Wind" layers work fine, but "Meteogram" and "Search" trigger the crash.
Please investigate the timezone conversion logic in the latest frontend update. Thanks!
-
I can second this. I was searching on here to see if anyone else was having the same issue. It seems to have started when the new UI update came out this month, and the issue persists on the new test version of windy as well. I get repeated crashes when trying to click on airports, meteograms, or changing to hourly forecast within the detailed forecast page with UTS times activated. I cannot post an error code as the page completely freezes and needs to be reloaded. But I can replicate it on any system I use as well.
-
@86weather @odcifis Hello, could you please test this behavior in our new Beta version of Windy? More info here.
-
"Hi Suty, I've tested the Beta version as suggested. Unfortunately, the behavior is identical to the stable version.
With UTC time enabled:- The Meteogram still fails to open and causes a total freeze.
- Searching for the first airport works, but the page crashes immediately when searching for a second airport.
The issue persists on both Chrome 143 (latest) and Chrome 109. It seems the current Beta hasn't resolved this specific timezone-related memory leak yet. Looking forward to further investigation. Thanks!"
-
@Suty I am getting the exact same fail points as ODCIFIS in the beta build as well.
-
I'm also experiencing this bug in Chrome/Edge and on the new map Beta Windy is testing right now. Here is my error console when the things freeze up:
{ "errorID": "uncaught-typeerror-cannot-read-properties-of-undefined-rea", "overlay": "radar", "runningPhase": "3_redrawFinished", "timestamp": 1769877894406, "runningMinutes": 0, "type": "error", "msg": "Uncaught TypeError: Cannot read properties of undefined (reading 'prev')", "url": "https://www.windy.com/airport/KIAH?radar,30.237,-93.108,8,p:metars", "ver": "49.0.0", "target": "index", "platform": "desktop", "device": "desktop", "latestBcast": "store: poisTemporary metars (32ms ago at 1769877894374) radar: loaded (23ms ago at 1769877894383) store: mapCoords (23ms ago at 1769877894383) store: lastPoiLocation (21ms ago at 1769877894385)", "network": { "downlink": 10, "effectiveType": "4g", "rtt": 50, "saveData": false }, "script": "effects.js", "line": 1, "col": 8402, "stack": "TypeError: Cannot read properties of undefined (reading 'prev') at https://www.windy.com/v/49.0.0.ind.6451/plugins/_shared/each.js:1:1247 at Y (https://www.windy.com/v/49.0.0.ind.6451/plugins/_shared/each.js:1:2495) at https://www.windy.com/v/49.0.0.ind.6451/plugins/_shared/each.js:1:3209 at Ge (https://www.windy.com/v/49.0.0.ind.6451/plugins/_shared/effects.js:1:17936) at Qe (https://www.windy.com/v/49.0.0.ind.6451/plugins/_shared/effects.js:1:19017) at Qt (https://www.windy.com/v/49.0.0.ind.6451/plugins/_shared/effects.js:1:12065) at zt.process (https://www.windy.com/v/49.0.0.ind.6451/plugins/_shared/effects.js:1:9276) at Gt (https://www.windy.com/v/49.0.0.ind.6451/plugins/_shared/effects.js:1:11591) at zt.flush (https://www.windy.com/v/49.0.0.ind.6451/plugins/_shared/effects.js:1:9716) at Array. (https://www.windy.com/v/49.0.0.ind.6451/plugins/_shared/effects.js:1:10232)" }{ "errorID": "uncaught-typeerror-cannot-read-properties-of-undefined-rea", "overlay": "radar", "runningPhase": "3_redrawFinished", "timestamp": 1769877894406, "runningMinutes": 0, "type": "error", "msg": "Uncaught TypeError: Cannot read properties of undefined (reading 'prev')", "url": "https://www.windy.com/airport/KIAH?radar,30.237,-93.108,8,p:metars", "ver": "49.0.0", "target": "index", "platform": "desktop", "device": "desktop", "latestBcast": "store: poisTemporary metars (32ms ago at 1769877894374) radar: loaded (23ms ago at 1769877894383) store: mapCoords (23ms ago at 1769877894383) store: lastPoiLocation (21ms ago at 1769877894385)", "network": { "downlink": 10, "effectiveType": "4g", "rtt": 50, "saveData": false }, "script": "effects.js", "line": 1, "col": 8402, "stack": "TypeError: Cannot read properties of undefined (reading 'prev') at https://www.windy.com/v/49.0.0.ind.6451/plugins/_shared/each.js:1:1247 at Y (https://www.windy.com/v/49.0.0.ind.6451/plugins/_shared/each.js:1:2495) at https://www.windy.com/v/49.0.0.ind.6451/plugins/_shared/each.js:1:3209 at Ge (https://www.windy.com/v/49.0.0.ind.6451/plugins/_shared/effects.js:1:17936) at Qe (https://www.windy.com/v/49.0.0.ind.6451/plugins/_shared/effects.js:1:19017) at Qt (https://www.windy.com/v/49.0.0.ind.6451/plugins/_shared/effects.js:1:12065) at zt.process (https://www.windy.com/v/49.0.0.ind.6451/plugins/_shared/effects.js:1:9276) at Gt (https://www.windy.com/v/49.0.0.ind.6451/plugins/_shared/effects.js:1:11591) at zt.flush (https://www.windy.com/v/49.0.0.ind.6451/plugins/_shared/effects.js:1:9716) at Array. (https://www.windy.com/v/49.0.0.ind.6451/plugins/_shared/effects.js:1:10232)" } -
@ScottyWxOH Hello, we already fixed this issue in the production version. Beta will get this fix with upcoming update.