Random crash when rendering with BI #39852

New Issue

Willi · 2014-04-23T03:34:28+02:00

Willi commented

2014-04-23 03:34:28 +02:00

System Information
Win7/64, AMD HD 6850

Blender Version
Broken:

til 2.58: no crash but also no render result (maybe version too old)
crash since 2.63 (r45996), including 2.70-1b523b5-win64

Short description of error
After narrowing the problem down (more and more and more...) from a big project to the simple scene attached, there's a random crash when starting rendering.

Exact steps for others to reproduce the error

Open the attached file: Layer one contains a group instance, layer 2 contains the group definition.
Go to layer 1 and render. Usually it crashes the first time. If not, render again until it crashes.

This is a very unspecific problem because it can be "solved" by any of the following actions:

Switch to Cycles
Clear Scale of the group instance (in layer 1), i.e. from 0.1 to 1.0
With the array modifier attached to the object in layer 2, reduce the count from 72 to 20 or less.
On layer 2, add the empty to the same group as the other object.

RandomCrash.blend

**System Information** Win7/64, AMD HD 6850 **Blender Version** Broken: - til 2.58: no crash but also no render result (maybe version too old) - crash since 2.63 (r45996), including 2.70-1b523b5-win64 **Short description of error** After narrowing the problem down (more and more and more...) from a big project to the simple scene attached, there's a random crash when starting rendering. **Exact steps for others to reproduce the error** - Open the attached file: Layer one contains a group instance, layer 2 contains the group definition. - Go to layer 1 and render. Usually it crashes the first time. If not, render again until it crashes. This is a very unspecific problem because it can be "solved" by *any of* the following actions: - Switch to Cycles - Clear Scale of the group instance (in layer 1), i.e. from 0.1 to 1.0 - With the array modifier attached to the object in layer 2, reduce the count from 72 to 20 or less. - On layer 2, add the empty to the same group as the other object. [RandomCrash.blend](https://archive.blender.org/developer/F85693/RandomCrash.blend)

Willi commented

2014-04-23 03:34:28 +02:00

Changed status to: 'Open'

Willi commented

2014-04-23 03:34:28 +02:00

Added subscriber: @willi-2

blender-admin commented

2014-04-23 19:07:45 +02:00

This issue was referenced by blender/blender-addons-contrib@1e6fa59e4f

This issue was referenced by blender/blender-addons-contrib@1e6fa59e4f4447bfeecd5abb868361ae1b7ab9ab

blender-admin commented

2014-04-23 19:07:45 +02:00

This issue was referenced by 1e6fa59e4f

This issue was referenced by 1e6fa59e4f4447bfeecd5abb868361ae1b7ab9ab

Campbell Barton commented

2014-04-23 19:09:13 +02:00

Changed status from 'Open' to: 'Resolved'

Campbell Barton closed this issue

2014-04-23 19:09:13 +02:00

Campbell Barton commented

2014-04-23 19:09:13 +02:00

Closed by commit 1e6fa59e4f.

Closed by commit 1e6fa59e4f.

Campbell Barton commented

2014-04-23 19:10:27 +02:00

Added subscriber: @ideasman42

Campbell Barton commented

2014-04-23 19:10:27 +02:00

Fixed, however the empty object should be in the group for correct results.

Note, the error is that the accumulated result of an array with a large offset causes an objects who's bounds exceeds the maximum float value (when added into the ray-tree).

Fixed, however the empty object should be in the group for correct results. Note, the error is that the accumulated result of an array with a large offset causes an objects who's bounds exceeds the maximum float value (when added into the ray-tree).

Willi commented

2014-04-23 19:23:56 +02:00

Thanks, but it crashes if the object is small (scale 0.1), not if it's large (scale 1.0). In addition, it didn't crash every time, and I don't see a large offset, and it works in cycles which doesn't change the geometry. So, I don't understand your explanation at all, but it's fine if it's fixed now. :)

Campbell Barton commented

2014-04-23 19:46:27 +02:00

@willi.

the array modifier gives different results at a different scale (evidentially not causing the ray-tree to reach INF)
just because it works sometimes, doesn't mean the bug is gone (it can accidentally work when the bug is present too :) )
cycles has its own ray-tree.

@willi. - the array modifier gives different results at a different scale (evidentially not causing the ray-tree to reach `INF`) - just because it works sometimes, doesn't mean the bug is gone (it can accidentally work when the bug is present too :) ) - cycles has its own ray-tree.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Random crash when rendering with BI #39852