Crash within a few frames with all renderers while rendering animation with animation nodes #61586

New Issue

Will D · 2019-02-15T19:46:37+01:00

Will D commented

2019-02-15 19:46:37 +01:00

System Information
Operating system: Windows 10
Graphics card: Nvidia 980Ti

Blender Version

2.80, 90f6fd0a36, blender2.8, 2019-02-15, 02:32 as found on the splash screen)

Short description of error
Guaranteed crash within rendering a few frames in Eevee or with cycles (render animation, render stills works ok), especially around frame 140
The file uses animation nodes, which work fine in the viewport so long as you scrub through first before you play the animation, but crashes when trying to render

Exact steps for others to reproduce the error
Open attached blend file, Set start frame to around 160 and hit render Animation, you will notice 2 things:

the plants controlled by animation nodes don't update, they render in whatever state they were last in the viewport as, (scrub through the viewport to see how they should behave)
blender will crash within a few frames.
BugreportBlenderCrashAnimationNodes.blend

**System Information** Operating system: Windows 10 Graphics card: Nvidia 980Ti **Blender Version** 2.80, 90f6fd0a3651, blender2.8, 2019-02-15, 02:32 as found on the splash screen) **Short description of error** Guaranteed crash within rendering a few frames in Eevee or with cycles (render animation, render stills works ok), especially around frame 140 The file uses animation nodes, which work fine in the viewport so long as you scrub through first before you play the animation, but crashes when trying to render **Exact steps for others to reproduce the error** Open attached blend file, Set start frame to around 160 and hit render Animation, you will notice 2 things: 1. the plants controlled by animation nodes don't update, they render in whatever state they were last in the viewport as, (scrub through the viewport to see how they should behave) 2. blender will crash within a few frames. [BugreportBlenderCrashAnimationNodes.blend](https://archive.blender.org/developer/F6620474/BugreportBlenderCrashAnimationNodes.blend)

Will D commented

2019-02-15 19:46:37 +01:00

Added subscriber: @Willd

Dalai Felinto commented

2019-02-15 20:35:13 +01:00

Added subscribers: @JacquesLucke, @dfelinto

Jacques Lucke was assigned by Dalai Felinto

2019-02-15 20:35:13 +01:00

Dalai Felinto commented

2019-02-15 20:35:13 +01:00

@JacquesLucke I didn't even confirm, but since this is animation nodes related, this is all yours.

Jacques Lucke commented

2019-02-15 21:08:41 +01:00

Changed status from 'Open' to: 'Archived'

Jacques Lucke closed this issue

2019-02-15 21:08:41 +01:00

Jacques Lucke commented

2019-02-15 21:08:41 +01:00

@Willd, please report this bug in the Bug Tracker of AN on GitHub.

I'm not sure if we can fix this currently, but I will check it when I'm back in Amsterdam.

Thanks :)

@Willd, please report this bug in the Bug Tracker of AN on GitHub. I'm not sure if we can fix this currently, but I will check it when I'm back in Amsterdam. Thanks :)

Will D commented

2019-02-15 22:05:10 +01:00

Hi, i've submitted it here.
https://github.com/JacquesLucke/animation_nodes/issues/1032

Hi, i've submitted it here. https://github.com/JacquesLucke/animation_nodes/issues/1032

Matt Wilson commented

2019-03-14 01:23:47 +01:00

Added subscriber: @mattdw

Matt Wilson commented

2019-03-14 01:23:47 +01:00

I triggered this from a debug Blender build; here's a stack trace:

https://gist.github.com/mattdw/a24e49bb7e7d6801976057f70e519d1d

It's happening in mesh_calc_modifiers in DerivedMesh.c, and appears to be bad/corrupt data – it might be an Animation Nodes problem, but it seems more likely that Animation Nodes is triggering an underlying condition. (A value which should probably be NULL is 0xddddddddddddddf0, which looks pretty suspicious to me…)

I'm brand new to Blender dev – let me know if I can provide any more info for you!

I triggered this from a debug Blender build; here's a stack trace: https://gist.github.com/mattdw/a24e49bb7e7d6801976057f70e519d1d It's happening in mesh_calc_modifiers in DerivedMesh.c, and appears to be bad/corrupt data – it might be an Animation Nodes problem, but it seems more likely that Animation Nodes is triggering an underlying condition. (A value which should probably be NULL is 0xddddddddddddddf0, which looks pretty suspicious to me…) I'm brand new to Blender dev – let me know if I can provide any more info for you!

Matt Wilson commented

2019-03-14 23:54:52 +01:00

It's happening all over the place, depending on what the Animation Nodes setup is manipulating, but it doesn't seem to happen at all when rendering headlessly. Could be a race between viewport and renderer?

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

Crash within a few frames with all renderers while rendering animation with animation nodes #61586