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
Describe the bug
It seems that joystick axis are leaking memory somewhere - we had a case in discord where user reports MF stopping functioning mid-flight and then turns out they have several joystick axis configured as inputs.
I can reproduce it myself.
For me I need to enable either info or debug log, and then move the axis back and forth, and with the above ~256 copies of the input config, everything works, but memory footprint grows 28MB each time I move the axis back and forth.
Steps To Reproduce
Steps to reproduce the behavior:
Add an input config for a joystick axis, @ 2.0001 / 16383 - -16383 max 16383 min (>K:ELEVATOR_SET)
Duplicate the input config say 100-200 times (ctrl-a, right click -> duplicate, ctrl-a .... repeat 10 times and you got enough..)
Enable logging
See memory footprint in task manager while moving the joystick axis.
Expected behavior
Do not grow the memory footprint constantly
Actual behavior
Memory footprint grows when joystick axis is moved. This seems related to logging for me, but the user who reported this on discord sees this also without logging.
Details
MobiFlight Version: 10.4.0
FlightSim: irrelevant (happens with MF variables too, even when no sim is running)
The text was updated successfully, but these errors were encountered:
Describe the bug
It seems that joystick axis are leaking memory somewhere - we had a case in discord where user reports MF stopping functioning mid-flight and then turns out they have several joystick axis configured as inputs.
I can reproduce it myself.
For me I need to enable either info or debug log, and then move the axis back and forth, and with the above ~256 copies of the input config, everything works, but memory footprint grows 28MB each time I move the axis back and forth.
Steps To Reproduce
Steps to reproduce the behavior:
Add an input config for a joystick axis,
@ 2.0001 / 16383 - -16383 max 16383 min (>K:ELEVATOR_SET)
Duplicate the input config say 100-200 times (ctrl-a, right click -> duplicate, ctrl-a .... repeat 10 times and you got enough..)
Enable logging
See memory footprint in task manager while moving the joystick axis.
Expected behavior
Do not grow the memory footprint constantly
Actual behavior
Memory footprint grows when joystick axis is moved. This seems related to logging for me, but the user who reported this on discord sees this also without logging.
Details
The text was updated successfully, but these errors were encountered: