You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Context: setting the bound of an instance to NaN eventually results in an error when collision logic is run.
Setting y = NaN on an instance doesn't directly cause a crash. However attempting to break in the debugger after y = NaN will cause the runner to crash and the runner to crash and the debugger to exit without breaking in the problem code.
Steps To Reproduce
Open attached project
Make sure there is a breakpoint set on line 6 of Object1 step event (this will be the var f = y line)
Run via the debugger
Observe that the game will freeze for a bit, then the runner will exit and the debugger will disconnect without ever breaking into the code
Clear the breakpoint and run again
Observe that without a breakpoint the game runs fine (there will be a black screen but the Debugger graph shows that the game is processing frames)
Which version of GameMaker are you reporting this issue for?
IDE v2024.600.0.579 Runtime v2024.600.0.605
Which operating system(s) are you seeing the problem on?
verified as of IDE v2024.800.0.599 Runtime v2024.800.0.622
YYDan
changed the title
Debugger disconnects when breaking in the IDE after an instance bound is set to NaN
Debugger: If an instance bound is set to NaN when hitting a breakpoint this crashes the game before that break happens
Aug 1, 2024
Description
Context: setting the bound of an instance to NaN eventually results in an error when collision logic is run.
Setting
y = NaN
on an instance doesn't directly cause a crash. However attempting to break in the debugger aftery = NaN
will cause the runner to crash and the runner to crash and the debugger to exit without breaking in the problem code.Steps To Reproduce
var f = y
line)Which version of GameMaker are you reporting this issue for?
IDE v2024.600.0.579 Runtime v2024.600.0.605
Which operating system(s) are you seeing the problem on?
Windows 10.0.19045.0
536a69a5-152c-45a6-9bc5-3a51bd1db96d
The text was updated successfully, but these errors were encountered: