View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0028957||Runner||Functions||Public||2018-02-21 09:24||2018-06-22 10:50|
|Reporter||Sam Cumming||Assigned To||Chris Harrison|
|Priority||High||Severity||A - Crash/Hang||Reproducibility||100%|
|Target Version||2.1.5||Fixed in Version||2.1.5|
|Summary||0028957: Functions: 'Instance_Change()' can duplicate objects into 1000s after 4 or 5 calls|
|Description||If you use the 'Instance_Change()' function, then execute some code on the changed instance, then change back to the original instance again (using Instance_Change), you will duplicate the original object exponentially, very quickly reaching 1000s of Instances. This leads to the Runner becoming unstable and unresponsive.|
In the attached project, if you open o_fox, you'll see that it calls Instance_Change(o_blank, true), and then in o_blank it modifies the position of the object before changing back to o_fox.
The attached project also has a workaround for the bug. According to the workaround, this behaviour only occurs when Instance_Change is called in the Create event. Moving the function to any other event will stop this bug from replicating.
|Steps To Reproduce||1. Open the attached project.|
2. Open o_fox and o_blank, observe that these objects swap between each other when left mouse is pressed.
3. Run the project.
4. Click multiple times, observe that the Instance count rapidly climbs, even though it shouldn't.
|Additional Information||The reporter mentions that this has been occurring since 184.108.40.206.|
|1.4 Found In||1.4.17|
|2.x Runtime Found In||220.127.116.11|
|2.x Runtime Verified In|