batch previews segfault on some materials #51734

New Issue

matali23 · 2017-06-07T16:20:16+02:00

matali23 commented

2017-06-07 16:20:16 +02:00

System Information
Windows 7 x64

Blender Version
Broken: 58a434b

Short description of error
when using file -> data previews -> batch-generate previews, it sometime crashes on some materials.

Exact steps for others to reproduce the error
File is from Blendermarket and is copyrighted, but I can provide the problematic bits per mail.

**System Information** Windows 7 x64 **Blender Version** Broken: 58a434b **Short description of error** when using file -> data previews -> batch-generate previews, it sometime crashes on some materials. **Exact steps for others to reproduce the error** File is from Blendermarket and is copyrighted, but I can provide the problematic bits per mail.

matali23 commented

2017-06-07 16:20:16 +02:00

Changed status to: 'Open'

matali23 commented

2017-06-07 16:20:16 +02:00

Added subscriber: @matali23

Dalai Felinto commented

2017-06-07 18:43:01 +02:00

Added subscriber: @dfelinto

Dalai Felinto commented

2017-06-07 18:43:01 +02:00

Please re-create the issue in a simple file that you can share. The simple the file the better. Append the problematic material in a blend new file, simplify it, change it, ...

matali23 commented

2017-06-07 20:24:09 +02:00

the file is simple, it's a cube with one material. But it's copyrighted. That's the only problem.

Fable Fox commented

2017-06-08 00:15:25 +02:00

Added subscriber: @fablefox

Fable Fox commented

2017-06-08 00:15:25 +02:00

does crash log generated? please upload if it does
https://docs.blender.org/manual/en/dev/troubleshooting/crash.html

does crash log generated? please upload if it does https://docs.blender.org/manual/en/dev/troubleshooting/crash.html

matali23 commented

2017-06-08 12:21:26 +02:00

it only writes segmentation fault in the command line. Other lines are startup messages with found python bundled.

Steffen Dünner commented

2017-06-08 12:24:37 +02:00

Added subscriber: @SteffenD

Dalai Felinto commented

2017-06-08 13:07:51 +02:00

Sorry but, claims that you cannot share because of copyright is not acceptable as excuse. As mentioned before you can just spend time on anonymizing the file (remove textures, remove parts of material that makes it recognizable). Or post the file here with the additional statement "File only can be used for debugging and fixing blender".

If you still think the Blender Market maker wouldn't like you to share it at any cost, contact her/him directly and explain the situation. Otherwise there is nothing we can do.

Worthy noting that this is a free service, by volunteers and supported by the Development Fund. More often than not the bug reporter is expected to invest some time on it as well.

Sorry but, claims that you cannot share because of copyright is not acceptable as excuse. As mentioned before you can just spend time on anonymizing the file (remove textures, remove parts of material that makes it recognizable). Or post the file here with the additional statement "File only can be used for debugging and fixing blender". If you still think the Blender Market maker wouldn't like you to share it at any cost, contact her/him directly and explain the situation. Otherwise there is nothing we can do. Worthy noting that this is a free service, by volunteers and supported by the Development Fund. More often than not the bug reporter is expected to invest some time on it as well.

mathieu menuet commented

2017-06-12 20:58:31 +02:00

Added subscriber: @bliblubli

mathieu menuet commented

2017-06-12 20:58:31 +02:00

I also have some Blendermarket materials, so I had a look as it may have come from cycles. It comes from the cgc_oak material. But what is impressive is although I spend a lot of time to bisect, only retaining a glossy shader and the material output is enough to reproduce the crash. Of course, neither the full nor the simplified material crash on normal rendering with cycles. So I think the problem doesn't come from cycles.
Here it is, a cube with 1 shader creating a seg fault:
test previews22.blend

I also have some Blendermarket materials, so I had a look as it may have come from cycles. It comes from the cgc_oak material. But what is impressive is although I spend a lot of time to bisect, only retaining a glossy shader and the material output is enough to reproduce the crash. Of course, neither the full nor the simplified material crash on normal rendering with cycles. So I think the problem doesn't come from cycles. Here it is, a cube with 1 shader creating a seg fault: [test previews22.blend](https://archive.blender.org/developer/F628536/test_previews22.blend)

Sergey Sharybin was assigned by Dalai Felinto

2017-06-13 12:28:42 +02:00

Dalai Felinto commented

2017-06-13 12:28:42 +02:00

Confirmed, crash log: P498

Confirmed, crash log: [P498](https://archive.blender.org/developer/P498.txt)

matali23 commented

2017-06-26 17:10:08 +02:00

thanks bliblubli, I never would have thought that a glossy shader alone could create the crash.