Crash: load new level; array modifier using curve length #38553

New Issue

Alex Fraser · 2014-02-09T05:03:15+01:00

Alex Fraser commented

2014-02-09 05:03:15 +01:00

System Information

Ubuntu 13.10, 64-bit; I think it happens on Windows too.
AMD Mobility Radeon HD 5430

Blender Version
Broken: 2.69 a7b1349 (31 Jan), 4393398, b105d2a
Worked: 2.69 7294c54 (23 Dec)

Short description of error

If a game loads a file that contains an object with an array modifier that uses a curve to set its length, blender/blenderplayer will segfault.

Exact steps for others to reproduce the error

Download and unzip: bge_curve_array_crash.zip
Load bge_loader.blend
Press P

The game will start and immediately load bge_curve_array_crash.blend. At that point, it will crash with this stack trace:

bge_curve_array_backtrace.txt

It seems that amd->curve_ob->curve_cache is null.

If you start the game from bge_curve_array_crash.blend (which contains the array object), it does not crash.

**System Information** Ubuntu 13.10, 64-bit; I think it happens on Windows too. AMD Mobility Radeon HD 5430 **Blender Version** Broken: 2.69 a7b1349 (31 Jan), 4393398, b105d2a Worked: 2.69 7294c54 (23 Dec) **Short description of error** If a game loads a file that contains an object with an array modifier that uses a curve to set its length, blender/blenderplayer will segfault. **Exact steps for others to reproduce the error** 1. Download and unzip: [bge_curve_array_crash.zip](https://archive.blender.org/developer/F76534/bge_curve_array_crash.zip) 1. Load `bge_loader.blend` 1. Press `P` The game will start and immediately load `bge_curve_array_crash.blend`. At that point, it will crash with this stack trace: [bge_curve_array_backtrace.txt](https://archive.blender.org/developer/F76535/bge_curve_array_backtrace.txt) It seems that `amd->curve_ob->curve_cache` is `null`. If you start the game from `bge_curve_array_crash.blend` (which contains the array object), it does not crash.

Alex Fraser commented

2014-02-09 05:03:15 +01:00

Changed status to: 'Open'

Alex Fraser commented

2014-02-09 05:03:15 +01:00

Added subscriber: @z0r

Alex Fraser commented

2014-02-09 10:28:47 +01:00

I ran a git bisect; it seems the first bad version is ac077f016d. Full log:
bge_curve_bisect.txt

I ran a `git bisect`; it seems the first bad version is ac077f016d3667a3b15853ac79b272cb0b6fd661. Full log: [bge_curve_bisect.txt](https://archive.blender.org/developer/F76564/bge_curve_bisect.txt)

Alex Fraser commented

2014-02-09 12:46:17 +01:00

Added subscriber: @Sergey

Alex Fraser commented

2014-02-09 12:46:17 +01:00

@Sergey, what do you think about this? To fix this, we could revert ac077f0 apart from the DAG node tagging part - but then we're back to needing a reference to the scene.

@Sergey, what do you think about this? To fix this, we could revert ac077f0 apart from the DAG node tagging part - but then we're back to needing a reference to the scene.

Sergey Sharybin self-assigned this 2014-02-10 07:10:55 +01:00

Sergey Sharybin commented

2014-02-10 07:10:55 +01:00

Would need to look further into this issue. All the stuff which is related on object evaluation should happen strictly in order defined in DAG and there should no be any if(data_is_not_ready) { prepare_data; } things.
But found some more cases when following this rule crashes. Will either find some proper solution or temporary revert the change or until proper solution is ready.

Would need to look further into this issue. All the stuff which is related on object evaluation should happen strictly in order defined in DAG and there should no be any `if(data_is_not_ready) { prepare_data; }` things. But found some more cases when following this rule crashes. Will either find some proper solution or temporary revert the change or until proper solution is ready.

blender-admin commented

2014-02-11 13:25:53 +01:00

This issue was referenced by blender/blender-addons-contrib@c0a13322cd

This issue was referenced by blender/blender-addons-contrib@c0a13322cdea417885ce9f88d0b42ff0ef62483c

blender-admin commented

2014-02-11 13:25:53 +01:00

This issue was referenced by c0a13322cd

This issue was referenced by c0a13322cdea417885ce9f88d0b42ff0ef62483c

Sergey Sharybin commented

2014-02-11 13:27:35 +01:00

Changed status from 'Open' to: 'Resolved'

Sergey Sharybin closed this issue