replaceMesh() / LibNew() crashing game engine #38170

New Issue

solarlune · 2014-01-12T16:59:44+01:00

solarlune commented

2014-01-12 16:59:44 +01:00

System Information
Windows 7 64-bit, AMD RADEON HD 7750

Blender Version
Broken: Recent 2.69 Buildbot Version
Hash 74216cf
Date 1/12/14

Worked: 2.69 Release (Note that the first two bugs don't happen in the release version, but the last one still does)

There's a few errors shown in this blend file. The first two are more critical, while the last one isn't game-breaking, but doesn't work correctly.

LibNewBug.blend

1 - When you use the LibNew() function on a recent version of Blender (like the one I posted above), and then escape out of it, it crashes Blender out.

2 - When you use the replaceMesh() function using a mesh that you know exists (in the example blend, it's the one currently on the object), it crashes Blender without even starting the game engine.

3 - When you use LibNew, it makes a new visual mesh, but not a physical mesh. You can see that the two different cubes share physical meshes in the "LibNewFail" scene.

To reproduce the errors, just switch to the corresponding scenes and press P to play the game engine on the provided blend file. You can also use LibNew() or replaceMesh() on a mesh on a new blend file.

**System Information** Windows 7 64-bit, AMD RADEON HD 7750 **Blender Version** Broken: Recent 2.69 Buildbot Version Hash 74216cf Date 1/12/14 Worked: 2.69 Release (Note that the first two bugs don't happen in the release version, but the last one still does) There's a few errors shown in this blend file. The first two are more critical, while the last one isn't game-breaking, but doesn't work correctly. [LibNewBug.blend](https://archive.blender.org/developer/F67242/LibNewBug.blend) 1 - When you use the LibNew() function on a recent version of Blender (like the one I posted above), and then escape out of it, it crashes Blender out. 2 - When you use the replaceMesh() function using a mesh that you know exists (in the example blend, it's the one currently on the object), it crashes Blender without even starting the game engine. 3 - When you use LibNew, it makes a new visual mesh, but not a physical mesh. You can see that the two different cubes share physical meshes in the "LibNewFail" scene. To reproduce the errors, just switch to the corresponding scenes and press P to play the game engine on the provided blend file. You can also use LibNew() or replaceMesh() on a mesh on a new blend file.

solarlune commented

2014-01-12 16:59:44 +01:00

Changed status to: 'Open'

solarlune commented

2014-01-12 16:59:44 +01:00

Added subscriber: @solarlune

Mitchell Stokes commented

2014-01-21 23:44:57 +01:00

Added subscriber: @Moguri

Mitchell Stokes commented

2014-01-21 23:44:57 +01:00

It looks like error 1 is caused by 709041, which looks like the threaded depsgraph commit. I wonder if the BGE is missing something for cleanup.

Mitchell Stokes commented

2014-01-21 23:52:52 +01:00

And error 2 is caused by 6a4733

solarlune commented

2014-02-23 08:53:12 +01:00

Bumping (?) for more info. I just tried this in the recent Release Candidate for Blender 2.7, and two of the bugs still seem to be there. The replaceMesh bug seems to have been fixed.

Sergey Sharybin commented

2014-02-23 10:37:00 +01:00

Added subscriber: @Sergey

Sergey Sharybin commented

2014-02-23 10:37:00 +01:00

@Moguri, #1 is caused by calloc-ing main in KX_PythonMain.cpp:755, you need to use BKE_main_new() to properly allocate bMain. One liner fix :)

Other things i'm not sure.

@Moguri, #1 is caused by calloc-ing main in KX_PythonMain.cpp:755, you need to use `BKE_main_new()` to properly allocate bMain. One liner fix :) Other things i'm not sure.

Mitchell Stokes commented

2014-02-23 21:58:32 +01:00

Thanks for the fix sergey. Any idea why we have BKE_main functions defined in BKE_library.h instead of BKE_main.h?

So, now 1 and 2 should be fixed. 3 sounds like a missing feature rather than a bug. I'm not sure if it will be tackled prior to 2.70 being released.

Thanks for the fix sergey. Any idea why we have BKE_main functions defined in BKE_library.h instead of BKE_main.h? So, now 1 and 2 should be fixed. 3 sounds like a missing feature rather than a bug. I'm not sure if it will be tackled prior to 2.70 being released.

Sergey Sharybin commented

2014-02-24 07:59:22 +01:00

@Moguri, i think it's historical question -- BKE_main_free() was in BKE_library at the time i've added BKE_main_new(). Not really fussed with wither leaving this as is or re-shuffling functions/headers.. You could poke cambo -- he loves doing cleanup like this :)

@Moguri, i think it's historical question -- `BKE_main_free()` was in BKE_library at the time i've added `BKE_main_new()`. Not really fussed with wither leaving this as is or re-shuffling functions/headers.. You could poke cambo -- he loves doing cleanup like this :)

Raf Colson commented

2014-07-04 18:17:17 +02:00

Added subscriber: @raco

Raf Colson commented

2014-07-04 18:17:17 +02:00

@solarlune: Could we maybe open a new task for this third issue (LibNew doesn't update Physics Mesh) so this can be closed? Or change the title?

solarlune commented

2014-07-05 02:28:15 +02:00

I would edit the title and change the main text, but even though I'm the owner of the task, for some reason I can't edit it. I can create a new task if necessary.