Significant Lag Upon Instance Selection

[gm-bug-reporter[bot]]

Description

Upon selecting an instance for the first time in a room, the IDE will lag. This also seems to only register the first click, because double-clicking will not open the instance's details window as usual and instead just focuses the instance.

This lag does not build up over time and seems to be approximately the same duration for each occurance. The kind of object does not make a difference either. This issue occurs in an identical fashion whether you select the instance through the instance list or click on the instance within the room viewer. Issue exists in IDE versions 2024.8.1 and 2024.6.2.

Steps To Reproduce

1. Launch GameMaker.
2. Open a new room tab.
3. Select an object instance.
4. Notice that the IDE lags.

Which version of GameMaker are you reporting this issue for?

IDE v2024.8.1.171 Runtime v2024.8.1.218

Which operating system(s) are you seeing the problem on?

Windows 10.0.19045.0

Attached Files

• InstanceLagBug.webm

f73b0a12-0691-46ef-b025-b159e3c8b471

[Zanderkat]

I should also note that:

• Even though this only occurs for the first instance you select after focusing the tab, this issue reoccurs when you move to a different tab and then return to the original tab.
• Deselecting an instance as your first action within the tab does not cause the lag, but if you select an instance after this, the lag will occur.

[Grisgram]

I think, this should join the club of #7599

[Zanderkat]

I also experience significant lag when closing room tabs (but not other tabs). This lag is variable in duration, even with the same room. The duration doesn't seem to be affected by the number of tabs open either, so it appears truly "random" unlike the lag described in the issue above.

I figured that since the behavior was a little different, I'd make a separate bug for this issue. Should I still do this or just keep this note here?

[Grisgram]

just keep it, @stuckie will see it anyways and decide whether he'll merge them or not. the room lag is mentioned in the issue above, that's why I brought it into the discussion here, any you are right, the room editor has the biggest lags. Its open/close behavior for sure has to do with the extreme lags we experience now - we don't know, what this editor scans/updates when opening/closing - maybe its iterating something through the entire project?

[stuckie]

Rooms are very complicated, and can easily touch a lot of other systems... we will take a look on Monday, thanks!

[stuckie]

Yes, this is very likely to be a duplicate of the core issue of #7599 but will keep it separate just now, thanks.

[stuckie]

This should be better as of the November betas, if you are in a position to verify this works as you expect?