Crash with smoke #61399

New Issue

Fred Gobry · 2019-02-11T00:56:15+01:00

Fred Gobry commented

2019-02-11 00:56:15 +01:00

System Information
Operating system: Windows 10
Graphics card: Nvidia 1070 GTX

Blender Version
Broken: blender-2.80.0-git.191b8951f7af-windows64
Worked: (optional)

Short description of error
Moving to the next frame on the timeline causes blender to crash.

Exact steps for others to reproduce the error
I open smoke.blend (which has a baked smoke sim on my machine), Z -> rendered, then move to the timeline and Right arrow. Boom.

This is my first bug submission on this project, let me know if I should provide other information, etc. Thanks!

**System Information** Operating system: Windows 10 Graphics card: Nvidia 1070 GTX **Blender Version** Broken: blender-2.80.0-git.191b8951f7af-windows64 Worked: (optional) **Short description of error** Moving to the next frame on the timeline causes blender to crash. **Exact steps for others to reproduce the error** I open [smoke.blend](https://archive.blender.org/developer/F6573677/smoke.blend) (which has a baked smoke sim on my machine), Z -> rendered, then move to the timeline and Right arrow. Boom. This is my first bug submission on this project, let me know if I should provide other information, etc. Thanks!

Fred Gobry commented

2019-02-11 00:56:15 +01:00

Added subscriber: @chbug

Fred Gobry commented

2019-02-11 00:58:18 +01:00

Forgot the full system info if needed.

system-info.txt

Forgot the full system info if needed. [system-info.txt](https://archive.blender.org/developer/F6573717/system-info.txt)

Philipp Oeser commented

2019-02-11 14:08:51 +01:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2019-02-11 14:08:51 +01:00

Cannot reproduce here.
First I thought it was a duplicate of #58471 (but now I cannot reproduce that other report either anymore...)

Cannot reproduce here. First I thought it was a duplicate of #58471 (but now I cannot reproduce that other report either anymore...)

Jacques Lucke commented

2019-02-11 14:18:01 +01:00

Added subscriber: @JacquesLucke

Jacques Lucke commented

2019-02-11 14:18:01 +01:00

I can't reproduce it either..

@chbug, can you reproduce this issue in new files as well?
Maybe also try a newer Blender version.

If you have access to another computer, you can also try it there to see if this problem is specific to your computer.

I can't reproduce it either.. @chbug, can you reproduce this issue in new files as well? Maybe also try a newer Blender version. If you have access to another computer, you can also try it there to see if this problem is specific to your computer.

Fred Gobry commented

2019-02-11 15:48:51 +01:00

I'll try to reproduce with an even more recent build than 0208, which is the version I also used to create the sample file. Also I'll try to discard the cache and bake again. If it turns out it's related to the baked data, is there a simple way to share the 30GB of cached data, or is it even worth it?

Fred Gobry commented

2019-02-15 02:40:13 +01:00

I can still reproduce it with Blender 2.80 rel. 2019/02/13. I can also reproduce it by discarding the baked files and regenerating them. When you attempted to reproduce, did you bake the smoke sim?

I can try to start with a fresh file, but given that baking takes 20 minutes, I might get lucky but if I need to fiddle with lots of parameters it might take a long time to set things up the same way. Given that the failing file was generated with rel. 2019/02/08, is there a solid reason to expect it to be any different anyways?

Alternatively, if you have pointers on how to extract a stack trace of the crash on a windows machine, I can try to do that. I'm more familiar with development on linux systems, but my beefier machine runs Windows.

I can still reproduce it with Blender 2.80 rel. 2019/02/13. I can also reproduce it by discarding the baked files and regenerating them. When you attempted to reproduce, did you bake the smoke sim? I can try to start with a fresh file, but given that baking takes 20 minutes, I might get lucky but if I need to fiddle with lots of parameters it might take a long time to set things up the same way. Given that the failing file was generated with rel. 2019/02/08, is there a solid reason to expect it to be any different anyways? Alternatively, if you have pointers on how to extract a stack trace of the crash on a windows machine, I can try to do that. I'm more familiar with development on linux systems, but my beefier machine runs Windows.

Sebastian Parborg commented

2019-02-18 11:17:13 +01:00

Added subscriber: @ZedDB

Sebastian Parborg commented

2019-02-18 11:17:13 +01:00

Does it not crash if you download this dll and copy it so its located in the same directory as 'blender.exe' and run Blender normally?

Does it not crash if you download [this dll ](https://download.blender.org/opengl/software-emulation/windows64/opengl32.dll) and copy it so its located in the same directory as 'blender.exe' and run Blender normally?

Fred Gobry commented

2019-02-25 02:40:05 +01:00

Same crash with the DLL (and blender being super slow before that, which was expected I guess).

Sebastian Parborg commented

2019-02-25 14:53:39 +01:00

Yes, that .dll forces blender to use software rendering. So now we know that this isn't an issue with your GPU drivers at least.

I can't reproduce this even if I bake the simulation, yes. It doesn't seem to crash when I move around the timeline in rendered mode.

Because it seems like none of the devs can reproduce this, can you see if you can reproduce this issue from scratch with a build from today?

Yes, that .dll forces blender to use software rendering. So now we know that this isn't an issue with your GPU drivers at least. I can't reproduce this even if I bake the simulation, yes. It doesn't seem to crash when I move around the timeline in rendered mode. Because it seems like none of the devs can reproduce this, can you see if you can reproduce this issue from scratch with a build from today?

Fred Gobry commented

2019-03-07 06:36:01 +01:00

Reproduced from scratch from today's build (see untitled.blend). You need to bake the sim, switch to rendered mode, and use Shift-Left & Shift-Right to jump in the timeline (with this file it wasn't enough to Shift-Right).

Also, I installed the dev environment and can provide full stack traces if it helps.

Reproduced from scratch from today's build (see [untitled.blend](https://archive.blender.org/developer/F6777818/untitled.blend)). You need to bake the sim, switch to rendered mode, and use Shift-Left & Shift-Right to jump in the timeline (with this file it wasn't enough to Shift-Right). Also, I installed the dev environment and can provide full stack traces if it helps.

Philipp Oeser commented

2019-05-03 12:36:16 +02:00

Also cannot reproduce here...

@chbug: did you have success getting a full stack trace?

Also cannot reproduce here... @chbug: did you have success getting a full stack trace?

Bastien Montagne commented

2019-05-16 12:06:35 +02:00

Added subscriber: @mont29