GE crashes when object from other scene is ended after adding it #41599

New Issue

Kayran Schmidt · 2014-08-27T13:40:42+02:00

Kayran Schmidt commented

2014-08-27 13:40:42 +02:00

System Information
Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.140303-2144)

         Language: German (Regional Setting: German)

System Manufacturer: Hewlett-Packard

     System Model: HP Pavilion dv7 Notebook PC
             BIOS: InsydeH2O Version 03.60.48F.17
        Processor: Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz (4 CPUs), ~2.3GHz
           Memory: 8192MB RAM

Available OS Memory: 8140MB RAM

        Page File: 3061MB used, 13215MB available
      Windows Dir: C:\Windows
  DirectX Version: DirectX 11

graphic cards:
Radeon (TM) HD 6490M
Mobile Intel(R) HD Graphics

Blender Version
official 7.1

Short description of error

its simple:
when the game runs a overlay scene is added
when you press enter, a textobject from a invisible layer of this overlay scene is added to the overlay scene, and has an framecount of 120 frames to disappear.

the bug:
when the ~ 2 seconds of the 120 frames are over, the program crashes,

and there is another bug related to:
the new object should be added at the coordinates of the plane present in the overlay layer, but its added somewhere else, thou every time at the same position

the script:

import bge
import GameLogic

con = bge.logic.getCurrentController()
scene = bge.logic.getCurrentScene()
ownerobject = con.owner
keyboard = bge.logic.keyboard

def main():

#a counter for time measure, it counts the logic steps

#overlay scene

  if 'addedOverlay'not in ownerobject:
      bge.logic.addScene("overlay", 1)
      ownerobject['addedOverlay'] = True

#get the scene list

  for scenex in bge.logic.getSceneList():
      ownerobject[scenex.name] = scenex

#define that on pressing enter, writemode is activated

  if keyboard.events[bge.events.ENTERKEY] == bge.logic.KX_INPUT_JUST_ACTIVATED:
      
      print(ownerobject["overlay"].objects)
      
      ownerobject["overlay"].addObject(ownerobject["overlay"].objectsInactive["commandList"], ownerobject["overlay"].objects["Plane"], 120)
      
      print(ownerobject["overlay"].objects)

main()

bug.blend

Exact steps for others to reproduce the error
just press p and then enter

**System Information** Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.140303-2144) ``` Language: German (Regional Setting: German) ``` System Manufacturer: Hewlett-Packard ``` System Model: HP Pavilion dv7 Notebook PC BIOS: InsydeH2O Version 03.60.48F.17 Processor: Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz (4 CPUs), ~2.3GHz Memory: 8192MB RAM ``` Available OS Memory: 8140MB RAM ``` Page File: 3061MB used, 13215MB available Windows Dir: C:\Windows DirectX Version: DirectX 11 ``` graphic cards: Radeon (TM) HD 6490M Mobile Intel(R) HD Graphics **Blender Version** official 7.1 **Short description of error** its simple: when the game runs a overlay scene is added when you press enter, a textobject from a invisible layer of this overlay scene is added to the overlay scene, and has an framecount of 120 frames to disappear. the bug: when the ~ 2 seconds of the 120 frames are over, the program crashes, and there is another bug related to: the new object should be added at the coordinates of the plane present in the overlay layer, but its added somewhere else, thou every time at the same position the script: import bge import GameLogic con = bge.logic.getCurrentController() scene = bge.logic.getCurrentScene() ownerobject = con.owner keyboard = bge.logic.keyboard def main(): ``` ``` #a counter for time measure, it counts the logic steps ``` ``` #overlay scene ``` if 'addedOverlay'not in ownerobject: bge.logic.addScene("overlay", 1) ownerobject['addedOverlay'] = True ``` #get the scene list ``` for scenex in bge.logic.getSceneList(): ownerobject[scenex.name] = scenex ``` #define that on pressing enter, writemode is activated ``` if keyboard.events[bge.events.ENTERKEY] == bge.logic.KX_INPUT_JUST_ACTIVATED: print(ownerobject["overlay"].objects) ownerobject["overlay"].addObject(ownerobject["overlay"].objectsInactive["commandList"], ownerobject["overlay"].objects["Plane"], 120) print(ownerobject["overlay"].objects) ``` main() ``` ``` [bug.blend](https://archive.blender.org/developer/F106985/bug.blend) **Exact steps for others to reproduce the error** just press p and then enter

Kayran Schmidt commented

2014-08-27 13:40:42 +02:00

Changed status to: 'Open'

Kayran Schmidt commented

2014-08-27 13:40:42 +02:00

Added subscriber: @Winnetou

Kayran Schmidt commented

2014-08-27 15:03:45 +02:00

pls do not make up your minds about the comments, i forgot to delete them, as i came across this error wehn programming a game, hence the comments

and i want to thank blender society for ever effort in advance

w

pls do not make up your minds about the comments, i forgot to delete them, as i came across this error wehn programming a game, hence the comments and i want to thank blender society for ever effort in advance w

Kayran Schmidt commented

2014-08-27 15:08:25 +02:00

sry that i didnt write all these comments in my post, but i just discovered something interesting:
it only crashes with textobjects, cubes or anything else works fine....

sry that i didnt write all these comments in my post, but i just discovered something interesting: it only crashes with textobjects, cubes or anything else works fine....

Raf Colson commented

2014-08-29 21:57:18 +02:00

Added subscriber: @raco

Raf Colson commented

2014-08-29 21:57:18 +02:00

Edit:

Looking at your blend more carefully made me realize I didn't reproduce it exactly as was explained. Sorry about that. I could reproduce it and my conclusion is that adding an object in an overlay scene through the controller of an object in the background scene causes Blender to crash.

In the blend attached you can see clearly that the same script works if it's run through the controller of the spawner in the overlay scene. However, if you deactivate it in the Logic Brick editor and activate the 'add_text' brick in the background scene instead, then the crash occurs.

Overlay_scene_add_object_bug.blend

I remember this crash was discussed somewhere, so it could be that this was reported already.

Edit: Looking at your blend more carefully made me realize I didn't reproduce it exactly as was explained. Sorry about that. I could reproduce it and my conclusion is that adding an object in an overlay scene through the controller of an object in the background scene causes Blender to crash. In the blend attached you can see clearly that the same script works if it's run through the controller of the spawner in the overlay scene. However, if you deactivate it in the Logic Brick editor and activate the 'add_text' brick in the background scene instead, then the crash occurs. [Overlay_scene_add_object_bug.blend](https://archive.blender.org/developer/F107380/Overlay_scene_add_object_bug.blend) I remember this crash was discussed somewhere, so it could be that this was reported already.

Kayran Schmidt commented

2014-08-30 18:45:21 +02:00

if it is already in discussion somewhere, i didn't find it as i searched the bug, sry
anyway, i found a other way to my goal, though,

and i am happy to had the opportunity to be part of blender developement once...

thank you for your comment

if it is already in discussion somewhere, i didn't find it as i searched the bug, sry anyway, i found a other way to my goal, though, and i am happy to had the opportunity to be part of blender developement once... thank you for your comment

Jorge Bernal commented

2014-09-28 03:31:17 +02:00

Added subscriber: @JorgeBernalMartinez

Jorge Bernal commented

2014-09-28 03:31:17 +02:00

@raco: I just checked your example and I can not reproduce the crash. In both options that you point out, I obtain the word "text" without any crash.
tested with current master (2.72RC)

@raco: I just checked your example and I can not reproduce the crash. In both options that you point out, I obtain the word "text" without any crash. tested with current master (2.72RC)

Raf Colson commented

2014-09-28 12:14:28 +02:00

Changed status from 'Open' to: 'Resolved'

Raf Colson closed this issue

2014-09-28 12:14:28 +02:00

Raf Colson self-assigned this 2014-09-28 12:14:28 +02:00

Raf Colson commented

2014-09-28 12:14:28 +02:00

Thanks lordloki. It seems to be fixed in 2.72RC.

Edit: Nope, I was wrong. Didn't test if it crashed on endObject(). But it does.

Thanks lordloki. It seems to be fixed in 2.72RC. Edit: Nope, I was wrong. Didn't test if it crashed on endObject(). But it does.

Raf Colson commented

2014-09-28 12:23:46 +02:00

Changed status from 'Resolved' to: 'Open'

Raf Colson reopened this issue

2014-09-28 12:23:46 +02:00

Raf Colson commented

2014-09-28 12:23:46 +02:00

Sorry guys, it's still broken. Press Return to add object, wait a second until Blender crashes when its removed from the scene.

Overlay_scene_remove_added_object_bug.blend

Sorry guys, it's still broken. Press Return to add object, wait a second until Blender crashes when its removed from the scene. [Overlay_scene_remove_added_object_bug.blend](https://archive.blender.org/developer/F113372/Overlay_scene_remove_added_object_bug.blend)

Raf Colson removed their assignment 2014-09-28 12:26:48 +02:00

Jorge Bernal commented

2014-09-28 13:37:20 +02:00

@raco: I confirm the bug now :-)