Game Engine addObject() crashes when adding a second object #38289
Labels
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
Interest: X11
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#38289
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Windows 7 and Ubuntu 12.04 (both result in crashes).
GTX580 1.5GB.
i7 3770k
Blender Version
Broken: 2.69.8
Worked: 2.68
Short description of error
Adding an object to the scene the first time works perfectly. Once the first object disappears, if you add another object with addObject(), the game engine crashes and blender exits to the desktop. Seems to of occurred after Sergey's changes to the depsgraph.
Exact steps for others to reproduce the error
Changed status to: 'Open'
Added subscriber: @NickPolet
Added subscriber: @Ace_Dragon
This seems like it's the other issue that caused trouble in one of my projects (the one that I tested in builds done beyond mid-December).
I will ask Campbell, Sergey ect... this though, are the issues caused by things such as the Multi-threaded depsgraph in the BGE going to be fixed or should the BGE team just go ahead and fork Blender with emphasis on game creation (maybe from a build before the depsgraph changes)?
Because if there's no plans to fix what gets broken in the BGE from general development, then the case of a full-blown fork can become very strong. I suggested this before and got answers saying it's not the time to consider it, but perhaps that time is coming.
Added subscriber: @brecht
There is no equivalent dependency graph in the game engine, that's not relevant there. Anyway, the problem is that if no one has time to fix issues in the game engine, they also don't have time to fork it which is even more work.
Added subscriber: @Moguri
This looks like a duplicate of #38237. If that's the case, then this crash is caused by revision 6a4733, which (I think) was committed around the same time as the multi-threaded depsgraph changes.
This comment was removed by @Moguri
This bug seems to be resolved after commit
51c32ac199
.Changed status from 'Open' to: 'Resolved'