addObject crashes BGE if used to repeatedly spawn an object. #38237

New Issue

Christopher Fryer · 2014-01-15T22:40:49+01:00

Christopher Fryer commented

2014-01-15 22:40:49 +01:00

System Information
Arch Linux 32
Lenovo #60
Radeon X1300

Blender Version
Broken: 2.69 5cd3212, also on version immediately previous (for Arch repos anyway)
Worked: 2.68 (as downloaded from blender.org)

Short description of error
Repeat use of addObject in BGE usually results in immediate crash. If it does not crash, there is a massive RAM usage spike that soon results in a crash or requires user intervention.

Exact steps for others to reproduce the error
In firetest1.blend, the trigger is on LEFTCTRLKEY, with movement on the arrow keys. Fire once, notice that movement and collisions still work fine. Fire again, blender crashes.

In firetest2.blend, the triggers are on LEFTCTRLKEY and LEFTSHIFTKEY, with movement on the arrow keys. Same steps as above, except notice that you can use both triggers without crashing. Crash only occurs when a trigger is used a second time.

Other notes
If KX_INPUT_ACTIVE instead of KX_INPUT_JUST_ACTIVATED is used, holding the trigger key will result in many object spawns, but a crash follows the key release. In this case it does not seem to wait for later spawn attempt to crash.

Also, rapid keypresses can result in a few objects being spawned before the crash. So there seems to be at least some delay to it.

Crash files for above blends:

firetest1.crash.txt

firetest2.crash.txt

**System Information** Arch Linux 32 Lenovo #60 Radeon X1300 **Blender Version** Broken: 2.69 5cd3212, also on version immediately previous (for Arch repos anyway) Worked: 2.68 (as downloaded from blender.org) **Short description of error** Repeat use of addObject in BGE usually results in immediate crash. If it does not crash, there is a massive RAM usage spike that soon results in a crash or requires user intervention. **Exact steps for others to reproduce the error** In [firetest1.blend](https://archive.blender.org/developer/F69083/firetest1.blend), the trigger is on LEFTCTRLKEY, with movement on the arrow keys. Fire once, notice that movement and collisions still work fine. Fire again, blender crashes. In [firetest2.blend](https://archive.blender.org/developer/F69087/firetest2.blend), the triggers are on LEFTCTRLKEY and LEFTSHIFTKEY, with movement on the arrow keys. Same steps as above, except notice that you can use both triggers without crashing. Crash only occurs when a trigger is used a second time. **Other notes** If KX_INPUT_ACTIVE instead of KX_INPUT_JUST_ACTIVATED is used, holding the trigger key will result in many object spawns, but a crash follows the key release. In this case it does not seem to wait for later spawn attempt to crash. Also, rapid keypresses can result in a few objects being spawned before the crash. So there seems to be at least some delay to it. Crash files for above blends: [firetest1.crash.txt](https://archive.blender.org/developer/F69095/firetest1.crash.txt) [firetest2.crash.txt](https://archive.blender.org/developer/F69096/firetest2.crash.txt)

Christopher Fryer commented

2014-01-15 22:40:49 +01:00

Changed status to: 'Open'

Christopher Fryer commented

2014-01-15 22:40:49 +01:00

Added subscriber: @Treefingers

Campbell Barton was assigned by Mitchell Stokes

2014-01-21 20:48:58 +01:00

Mitchell Stokes commented

2014-01-21 20:48:58 +01:00

Added subscriber: @Moguri

Mitchell Stokes commented

2014-01-21 20:48:58 +01:00

Looks like this is caused by 6a4733. Changing the #if 0 to #if 1 in RAS_MeshObject::RemoveFromBuckets() gets rid of the crash. Assigning this to Campbell.