Latest blender build from this morning (52169).
Trying to open an OpenEXR multilayer file (exported from another blend file using the same build of blender). The file is compressed with ZIP.
Blender crashes as soon as you click the "Open Image" button in the file browser window.
Blender crashes with "Bus error: 10"
No point attaching a blend file as this was the first thing I tried doing in a fresh blend.
Tried submitting this bug with the exr attached below, but it didn't seem to work (file to big probably...), so here's the dropbox link to download:
https://dl.dropbox.com/u/39566862/blender/shot-13-0001.exr
This crashes on two computers. A Hackintosh running 10.7.5 and a macbook pro running 10.8.2
Description
Description
Event Timeline
Comment Actions
Sorry, seems to be a problem with the exr file. Let me do some more testing and I'll update
Comment Actions
Ok. After a bit of poking around, it seems to be an error with adding the diffuse indirect pass to the open exr file in the compositor using the File Output node. The file writes out ok, but as soon as Blender tries to open the openEXR, it crashes.
I've attached a test blend which shows this working. Two scenes, one for rendering, one for compositing.
Thanks.
Comment Actions
I am investigating that exr already - something fishy in it... thanks for the report!
Comment Actions
Thanks Ton.
Also, just tried to export another exr from the compositor and it has frozen the destination drive (external USB ExFAT drive). Was testing to make sure it was indeed just the diffuse indirect pass causing the trouble. Pretty sure it's Blender making the drive freeze as I'm not doing anything else (no other applications open).
Comment Actions
The new Multilayer out node was not respecting name conventions in our exr code (allowing too long names).
Pass names were hardcoded in blender before! Your passes had too long names. If you make them 10 chars or less things should work fine.
Fix in svn will allow names (layer+pass) up to 64 characters now.
What goes on with the USB drive I have no clue about - but this bug might cause severe memory errors. Be careful or use Blender revision 52183 or later.