[2.0.65] Freeze closing map view with Py suite + LTN

[MANBANMAN]

TL;DR
Regression between 2.0.64 → 2.0.65: closing the map view consistently freezes for ~30s in a large Py+LTN save (~1400–1800 stations). Opening the map is instant. Debug shows a huge “Update” spike. Save + log + screenshot attached.

Description
On version 2.0.65 experimental, closing the map view consistently freezes the game for ~30 seconds before resuming.
Opening the map is instant and works normally; only closing triggers the freeze.
This issue did not occur on 2.0.64 with the exact same mods and save.
I also tested on a 2-week old backup save (~1500 stations instead of ~1800). The same freeze happens when closing the map view in 2.0.65. This confirms it’s not caused by recent base expansion or a bad station setup — the issue appears even on an older, stable version of the same factory.
During the freeze the FPS counter drops sharply, then returns to 60 as soon as the game unfreezes.
Also happened on the main menu background simulation until I disabled that option in settings.

Steps to reproduce
Launch Factorio 2.0.65 with Py suite + LTN enabled.
Load a large save (~1400–1800 LTN stations).
Open map view (works normally).
Close map view → freeze for ~30s.

Expected
Closing the map should return immediately to gameplay.

Actual
Game hangs for ~30s with CPU usage dropping to near zero, then resumes normally.

Notes
Removing GUI-heavy mods (Helmod, LTN Manager, Bottleneck Lite) does not resolve the issue.
Debug show-time-usage shows one massive spike in Update (~282s) and smaller Lua spikes from LTN (~1.5s).
Happens even on a 2-week old backup save (~1500 stations), so it’s not from recent expansion.
Hardware: i9-14900K, RTX 5090, 32 GB RAM.

[Rseding91]

Thanks for the report. I was not able to reproduce this - however I noticed this line in the log file:

12.280 Error SteelSeriesGameSenseWindowsController.cpp:375: GameSense post BITMAP_EVENT failed: event: bind_game_event, 500, 0, (), {"error": {"message": "Something bad happened"}}

Does it still happen for you if you disable the keyboard LED integration in the settings? (settings -> other)

[MANBANMAN]

yeah looks like that did it.
thanks for the help, looks like its a steelseries problem then