Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CBA_fnc_addKeybind memory exhaustion #715

Closed
MaHuJa opened this issue Jul 1, 2017 · 4 comments
Closed

CBA_fnc_addKeybind memory exhaustion #715

MaHuJa opened this issue Jul 1, 2017 · 4 comments
Labels

Comments

@MaHuJa
Copy link

MaHuJa commented Jul 1, 2017

Arma 3 Version: 1.72 current stable
CBA Version: 3.4.0 'stable'. (3.3.1 tested to work).

Mods:

- CBA_A3

Description:

Steps to reproduce:

  • In controls, user, set 'user action 20' to alt+` (key left of 1)
  • Run
tmp = [(ActionKeys "User20" select 0),[false,false,false]];
["ALiVE","openMenu", "Open Menu (Requires Restart)", {playsound "HintCollapse"}, {}, tmp] call CBA_fnc_addKeybind;

FWIW (ActionKeys "User20" select 0) returns 9.39524e+008 in this case.

Where did the issue occur?

  • On game start if running @alive mod, else done in editor.

RPT log file:

@PabstMirror
Copy link
Contributor

Key codes above 255 don't make sense
https://community.bistudio.com/wiki/actionKeys
has some info on the mess that the command returns, but it doesn't seem usable if it's bound with modifies

#638 (comment) - life found a way 😄

@MaHuJa
Copy link
Author

MaHuJa commented Jul 1, 2017

A change on the repro - I unbound the user20 key, so the tmp was printed as [<null>,[false,false,false]] and the issue still occurs.

@PabstMirror
Copy link
Contributor

Start editor and open debug console and run

tmp = [0,[false,false,false]];
["ALiVE","openMenu", "Open Menu (Requires Restart)", {playsound "HintCollapse"}, {}, tmp, false, 0, true] call CBA_fnc_addKeybind;

Hopefully that should overwrite the saved setting in your profile and fix the issue for now

@MaHuJa
Copy link
Author

MaHuJa commented Jul 1, 2017

Next repro was setting appmenu (22) and it crashed. Calling it with 0 did not crash. After which 22 also worked.

Conclusion: running it with tmp = [0,[false,false,false]]; fixed the problem, and apparently (combined with a sane keybind value) permanently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants