Collision Sensor - R6025 pure virtual function call crash #30477

Closed
opened 2012-03-07 09:57:01 +01:00 by Riyuzakisan · 3 comments

Category: Physics

%%%Blender 2.62.0 (r44136); 32 bit
OS: Windows 7; 64 bit

There are two scenes involved: Main and Overlay. They are named accordingly in the attached .blend file.

The Main scene contains a Camera. On the Camera, there is an Always sensor connected to a Python script controller, which runs a script that adds the Overlay scene via the "bge.logic.addScene()" function. The Camera also has a Keyboard sensor (Spacebar key) that connects to the same script controller that adds the Overlay scene.

The Overlay scene contains a dynamic Cube object and a static Plane. The Cube has a Collision sensor set to detect the property "prop", and this sensor is connected to an And controller. The Plane has a property named "prop", to be detected by the Collision sensor.

The game is intended to be started in the Main scene. The "Overlay" scene is added by the script on startup. The Cube will fall and collide with the Plane. The script can then be triggered by the Keyboard sensor. Upon doing so, the script detects that the keyboard sensor is positive and gets the Object list from the Overlay scene. From this list, it gets the Plane object, and then deletes it using the KX_GameObject.endObject() function.

Deleting the Plane object that is being detected by the Collision sensor on the Cube causes Blender to immediately stop responding and then crash. Looking in the console window as the crash occurs, the following is printed:

"R6025

  • pure virtual function call"

Under different conditions, I have also observed a very slightly different error being printed upon the crash:

"R6205

  • pure virtual function call"

I have tested this under the conditions listed above with the Near sensor as well, which also causes Blender to crash with the "R6025" error.

In summary, it would seem that the error is caused by deleting objects in an overlayed scene that are being detected by a collision sensor.%%%

**Category**: Physics %%%Blender 2.62.0 (r44136); 32 bit OS: Windows 7; 64 bit There are two scenes involved: Main and Overlay. They are named accordingly in the attached .blend file. The Main scene contains a Camera. On the Camera, there is an Always sensor connected to a Python script controller, which runs a script that adds the Overlay scene via the "bge.logic.addScene()" function. The Camera also has a Keyboard sensor (Spacebar key) that connects to the same script controller that adds the Overlay scene. The Overlay scene contains a dynamic Cube object and a static Plane. The Cube has a Collision sensor set to detect the property "prop", and this sensor is connected to an And controller. The Plane has a property named "prop", to be detected by the Collision sensor. The game is intended to be started in the Main scene. The "Overlay" scene is added by the script on startup. The Cube will fall and collide with the Plane. The script can then be triggered by the Keyboard sensor. Upon doing so, the script detects that the keyboard sensor is positive and gets the Object list from the Overlay scene. From this list, it gets the Plane object, and then deletes it using the KX_GameObject.endObject() function. Deleting the Plane object that is being detected by the Collision sensor on the Cube causes Blender to immediately stop responding and then crash. Looking in the console window as the crash occurs, the following is printed: "R6025 - pure virtual function call" Under different conditions, I have also observed a very slightly different error being printed upon the crash: "R6205 - pure virtual function call" I have tested this under the conditions listed above with the Near sensor as well, which also causes Blender to crash with the "R6025" error. In summary, it would seem that the error is caused by deleting objects in an overlayed scene that are being detected by a collision sensor.%%%
Author

Changed status to: 'Open'

Changed status to: 'Open'

%%%Thanks for the report. Fixed in rev. 50027 (through a patch sent to the tracker)%%%

%%%Thanks for the report. Fixed in rev. 50027 (through a patch sent to the tracker)%%%

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#30477
No description provided.