Environment maps cause a hard crash with OSL enabled #40971

New Issue

Ante Vukorepa · 2014-07-06T20:44:49+02:00

Ante Vukorepa commented

2014-07-06 20:44:49 +02:00

System Information
Windows 8.1 Pro

Blender Version
Broken: 2.71 final, 2.71 RCs
Worked: unknown

Assigning World an Environment Texture results in a hard crash at render time (no crash log, no debug information in the console).

Exact steps for others to reproduce the error

Open default scene
Enable Open Shader Language
Add shader nodes to World Surface
Assign Background to World Surface shader
Assign an Environment Texture to Background
Hit Render (or change the Viewport Shading to Rendered)

Tested and confirmed to occur with EXRs and JPGs.
Not tested with TIFFs.

Test scene: OSL_crash.blend

**System Information** Windows 8.1 Pro **Blender Version** Broken: 2.71 final, 2.71 RCs Worked: unknown Assigning World an Environment Texture results in a hard crash at render time (no crash log, no debug information in the console). **Exact steps for others to reproduce the error** 1. Open default scene 2. Enable Open Shader Language 3. Add shader nodes to World Surface 4. Assign Background to World Surface shader 5. Assign an Environment Texture to Background 6. Hit Render (or change the Viewport Shading to Rendered) Tested and confirmed to occur with EXRs and JPGs. Not tested with TIFFs. Test scene: [OSL_crash.blend](https://archive.blender.org/developer/F96852/OSL_crash.blend)

Ante Vukorepa commented

2014-07-06 20:44:49 +02:00

Changed status to: 'Open'

Ante Vukorepa commented

2014-07-06 20:44:49 +02:00

Added subscriber: @orcinus

blender-admin commented

2014-07-06 20:44:49 +02:00

#41123 was marked as duplicate of this issue

blender-admin commented

2014-07-06 20:44:49 +02:00

#40972 was marked as duplicate of this issue

Ante Vukorepa commented

2014-07-06 20:48:28 +02:00

The test EXR texture is packed in the file.
Just tested this in Blender 2.70a for Mac OS X and it works fine there.
Will test on 2.71 for Mac OS as well as 2.70 for Windows.

The test EXR texture is packed in the file. Just tested this in Blender 2.70a for Mac OS X and it works fine there. Will test on 2.71 for Mac OS as well as 2.70 for Windows.

Bastien Montagne commented

2014-07-06 20:50:50 +02:00

Added subscriber: @mont29

Bastien Montagne commented

2014-07-06 20:50:50 +02:00

Can confirm crash with current master on linux64 as well :/

Ante Vukorepa commented

2014-07-06 21:03:18 +02:00

Does not crash on 2.71 Mac OS.
Does not crash on 2.70a Windows x64.

CRASHES on 2.70a Windows x64 VC2013 preview.

Does not crash on 2.71 Mac OS. Does not crash on 2.70a Windows x64. CRASHES on 2.70a Windows x64 VC2013 preview.

Sergey Sharybin commented

2014-07-07 08:49:23 +02:00

Added subscribers: @MartijnBerger, @ThomasDinges, @Sergey

Sergey Sharybin commented

2014-07-07 08:49:23 +02:00

The crahs of current master and packed image has been fixed. However, it's a crash on a new code which was added after 2.71 release in order to support packed images render.

Original report about crash crash of 2.71 i can not reproduce neither on linux nor on windows7. Could be something really platform-dependent like #40884.

@ThomasDinges, @MartijnBerger, are you able to reproduce crash?
@orcinus, are you able to reproduce the crahs NOT using packed images with latest builds from builder.blender.org?

The crahs of current master and packed image has been fixed. However, it's a crash on a new code which was added after 2.71 release in order to support packed images render. Original report about crash crash of 2.71 i can not reproduce neither on linux nor on windows7. Could be something really platform-dependent like #40884. @ThomasDinges, @MartijnBerger, are you able to reproduce crash? @orcinus, are you able to reproduce the crahs NOT using packed images with latest builds from builder.blender.org?

Sergey Sharybin commented

2014-07-07 08:50:22 +02:00

◀ Merged tasks: #40972.

Ante Vukorepa commented

2014-07-07 16:37:25 +02:00

@Sergey The crash occurs with or without packed images. In fact, i can just leave an empty Image Texture node (without a texture loaded) connected to a shader and it will still crash.
Downloading buildbot version(s) now, will report when i test.

Just FYI, i have a strong hunch this is an interaction between Windows 8(.1) and VC2013.
If true, that might mean @mont29's linux reproduction is something else.

@Sergey The crash occurs with or without packed images. In fact, i can just leave an empty Image Texture node (without a texture loaded) connected to a shader and it will still crash. Downloading buildbot version(s) now, will report when i test. Just FYI, i have a strong hunch this is an interaction between Windows 8(.1) and VC2013. If true, that might mean @mont29's linux reproduction is something else.

Ante Vukorepa commented

2014-07-07 16:52:40 +02:00

blender-2.71-4299b00-win64 - CRASHES
blender-2.71-81c3fc9-win64-vc9 - DOES NOT crash

blender-2.71-4299b00-win64 - **CRASHES** blender-2.71-81c3fc9-win64-vc9 - **DOES NOT** crash

Ante Vukorepa commented

2014-07-07 17:26:54 +02:00

By the way, note that #40884 reproduction wasn't really undertaken correctly.
The original bug was reported on Windows 8.1 (hint hint), while the OP's resolution was:

but on my main Blender station, a Windows 7 64-bit desktop with a GTX 580 GPU, the same Blender version under the same conditions does not crash

So, once again... Strong hunch this has to do with VC2013 under Windows 8(.1).

By the way, note that #40884 reproduction wasn't really undertaken correctly. The original bug was reported on Windows 8.1 (hint hint), while the OP's resolution was: *but on my main Blender station, a **Windows 7** 64-bit desktop with a GTX 580 GPU, the same Blender version under the same conditions does not crash* So, once again... Strong hunch this has to do with VC2013 under Windows 8(.1).

Ante Vukorepa commented

2014-07-07 17:32:01 +02:00

In case this helps, here are the Event Viewer crash dumps:

Faulting application name: blender.exe, version: 2.7.1.0, time stamp: 0x53ba01cb
Faulting module name: blender.exe, version: 2.7.1.0, time stamp: 0x53ba01cb
Exception code: 0xc0000005
Fault offset: 0x0000000000e5460a
Faulting process id: 0x3f94
Faulting application start time: 0x01cf99f1bb9699cd
Faulting application path: C:\Users\Ante Vukorepa\Downloads\blender-2.71-4299b00-win64\blender-2.71-4299b00-win64\blender.exe
Faulting module path: C:\Users\Ante Vukorepa\Downloads\blender-2.71-4299b00-win64\blender-2.71-4299b00-win64\blender.exe
Report Id: 29c9dd68-05e5-11e4-82bc-a7a4915d524a
Faulting package full name: 
Faulting package-relative application ID:

Fault bucket 85940633048, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: blender.exe
P2: 2.7.1.0
P3: 53ba01cb
P4: blender.exe
P5: 2.7.1.0
P6: 53ba01cb
P7: c0000005
P8: 0000000000e5460a
P9: 
P10: 

Attached files:
C:\TempTemp\WER9FD7.tmp.WERInternalMetadata.xml

These files may be available here:
C:\Users\Ante Vukorepa\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_blender.exe_cff221b631569d13a3dc194097c173d2abe88c6_3918f389_2acfa5b3

Analysis symbol: 
Rechecking for solution: 0
Report Id: 29c9dd68-05e5-11e4-82bc-a7a4915d524a
Report Status: 1
Hashed bucket: 46621339fb80236b57f59351b166c6d4

WER file: Report.wer

In case this helps, here are the Event Viewer crash dumps: ``` Faulting application name: blender.exe, version: 2.7.1.0, time stamp: 0x53ba01cb Faulting module name: blender.exe, version: 2.7.1.0, time stamp: 0x53ba01cb Exception code: 0xc0000005 Fault offset: 0x0000000000e5460a Faulting process id: 0x3f94 Faulting application start time: 0x01cf99f1bb9699cd Faulting application path: C:\Users\Ante Vukorepa\Downloads\blender-2.71-4299b00-win64\blender-2.71-4299b00-win64\blender.exe Faulting module path: C:\Users\Ante Vukorepa\Downloads\blender-2.71-4299b00-win64\blender-2.71-4299b00-win64\blender.exe Report Id: 29c9dd68-05e5-11e4-82bc-a7a4915d524a Faulting package full name: Faulting package-relative application ID: ``` ------ ``` Fault bucket 85940633048, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: blender.exe P2: 2.7.1.0 P3: 53ba01cb P4: blender.exe P5: 2.7.1.0 P6: 53ba01cb P7: c0000005 P8: 0000000000e5460a P9: P10: Attached files: C:\TempTemp\WER9FD7.tmp.WERInternalMetadata.xml These files may be available here: C:\Users\Ante Vukorepa\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_blender.exe_cff221b631569d13a3dc194097c173d2abe88c6_3918f389_2acfa5b3 Analysis symbol: Rechecking for solution: 0 Report Id: 29c9dd68-05e5-11e4-82bc-a7a4915d524a Report Status: 1 Hashed bucket: 46621339fb80236b57f59351b166c6d4 ``` WER file: [Report.wer](https://archive.blender.org/developer/F96972/Report.wer)

Sergey Sharybin commented

2014-07-10 15:05:45 +02:00

I've committed some fixed at 5e216a6. Please grab a build which includes this commit and give it a test.

I've committed some fixed at 5e216a6. Please grab a build which includes this commit and give it a test.

Ante Vukorepa commented

2014-07-13 03:47:07 +02:00

Unsure how to check which build contains commits up to what, but if blender-2.71-5e3e095-win64 contains it, the problem is still there.

Sergey Sharybin commented

2014-07-13 09:34:49 +02:00

This build contains the fix i was referring to. Can not reproducethe crash atm tho.

@ThomasDinges, @MartijnBerger, mind having it a try?

This build contains the fix i was referring to. Can not reproducethe crash atm tho. @ThomasDinges, @MartijnBerger, mind having it a try?

Martijn Berger commented

2014-07-13 09:36:42 +02:00

I cannot reproduce the crash on a virtual machine where AVX is turned of even with 2.71 release.

I am thinking llvm as the real culprit

I cannot reproduce the crash on a virtual machine where AVX is turned of even with 2.71 release. I am thinking llvm as the real culprit

Sergey Sharybin commented

2014-07-24 15:04:26 +02:00

I'll merge #41123 in here since root of the issues are likely goes to the same thing.

Sergey Sharybin commented

2014-07-24 15:04:38 +02:00

Added subscribers: @joel.godin, @lichtwerk, @sambler

Sergey Sharybin commented

2014-07-24 15:04:38 +02:00

◀ Merged tasks: #41123.

Sergey Sharybin commented

2014-08-07 21:27:31 +02:00

Please test whether latest builds from builder.blender.org. We've upgraded both LLVM and OSL, this might have solved the issue.

Joel Godin commented

2014-08-07 22:25:25 +02:00

Works fine now on OSX 10.9 for both this blend file and one from #41123.
Thanks.

Works fine now on OSX 10.9 for both this blend file and one from #41123. Thanks.

Sergey Sharybin commented

2014-08-08 15:34:50 +02:00

Changed status from 'Open' to: 'Resolved'

Sergey Sharybin closed this issue

2014-08-08 15:34:50 +02:00

Sergey Sharybin self-assigned this 2014-08-08 15:34:50 +02:00

Sergey Sharybin commented

2014-08-08 15:34:50 +02:00

Will assume the issue fixed now for everyone. @orcinus lemme know if it still happens for you.

Ante Vukorepa commented

2014-08-08 15:44:59 +02:00

@joel.godin Mac OS never exhibited the bug.

@Sergey Will retest in a few weeks (stuck on an island without access to my Windows desktop) and report back if it's still broken.

@joel.godin Mac OS never exhibited the bug. @Sergey Will retest in a few weeks (stuck on an island without access to my Windows desktop) and report back if it's still broken.

Joel Godin commented

2014-08-08 16:53:38 +02:00

@orcinus Yes, it did if you read the bug I reported at #41123 which was merged with this one. :)

Ante Vukorepa commented

2014-08-09 00:27:13 +02:00

Ah, gotcha, sorry :)
Didn't experience that one.

Ah, gotcha, sorry :) Didn't experience that one.

Ante Vukorepa commented

2014-08-30 23:48:52 +02:00

Issue has not been fixed.

Tested with blender-2.71-526ae63-win64, same scene as posted in the original report, still crashes when you hit render or switch viewport shading to rendered.

(on Windows 8.1, as in the original report)

Issue has not been fixed. Tested with blender-2.71-526ae63-win64, same scene as posted in the original report, still crashes when you hit render or switch viewport shading to rendered. (on Windows 8.1, as in the original report)

Sergey Sharybin commented

2014-09-01 09:27:53 +02:00

@orcinus, so far we can not reproduce the issue. Did you try reproducing the issue on another computer?

Ante Vukorepa commented

2014-09-01 23:01:37 +02:00

Yes i did.
i7 laptop (Asus Taichi) running Windows 8 (not .1) x64.

Exact same behaviour.
Have you tried reproducing it on Windows 8 (NOT 7)?

Yes i did. i7 laptop (Asus Taichi) running Windows 8 (not .1) x64. Exact same behaviour. Have you tried reproducing it on Windows 8 (NOT 7)?

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

Environment maps cause a hard crash with OSL enabled #40971