View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0030068||Runner||Functions||Public||2018-10-04 12:24||2019-01-04 16:05|
|Reporter||Dan||Assigned To||Mike Dailly|
|Priority||Very High||Severity||A - Crash/Hang||Reproducibility||100%|
|Platform||OS||Windows 10||OS Version||Pro x64|
|Target Version||2.2.0||Fixed in Version||2.2.0|
|Summary||0030068: Functions: Crash when using get_string_async() and get_integer_async()|
|Description||Runtime v184.108.40.2068 has a crash when using get_string_async() and get_integer_async() and clicking either of the OK or Cancel buttons.|
This does not reproduced in internal versions, so must have been a temp issue we have since fixed.
|Steps To Reproduce||1. Run the attached sample for Windows (Android has also been reported).|
2. Use the dialog.
3. Observe game hard crashes (no code error is shown).
|Tags||No tags attached.|
|1.4 Found In|
|2.x Runtime Found In||220.127.116.118|
|2.x Runtime Verified In||18.104.22.1689|
get_async_bug.yyz (12,684 bytes)
|Fixed in green|
||Windows is fine now. Need to confirm Android.|
||Windows, UWP, Android, and HTML5 are all fine now. Closing.|
Please be aware this was a fairly general memory corruption issue which most commonly presented with async dialogues, but was not limited to that scenario - e.g., we think it's also the reason why a small number of users see crash dialogs on closing Windows games in 22.214.171.1248.