Current stable version: 0.1.1
Home › YafaRay › Issues

Save as EXR crash

Sat, 18/04/2009 - 14:24 — Bjo
Project:YafaRay
Version:0.1.x
Component:Code
Category:bug report
Priority:minor
Assigned:DarkTide
Status:needs review
Description

I use Blender 2.48a and Yafaray r302 on Xubuntu 8.10 Intrepid

When I try to save a render as an EXR image Yafaray + Blender crash everytimes.

Save as PNG, JPEG or other formats run well but not as EXR.

AttachmentSize
Capture.png24.22 KB

Comments

Sat, 18/04/2009 - 16:34 — admin

#1

I cannot reproduce the problem with linux (Fedora) + blender2.48a + YafaRay-0.1.0.302

It would be useful to know in your case:

1. It's the first time you try to save as EXR? What happens with previous versions? (Besides latest patches does not involves QT Gui)

2. The console says something? what it says? (Maybe running blender from a console and not from it's icon should not crash the console itself so you should be able to see error messages)

Sun, 19/04/2009 - 22:35 — Bjo

#2

Ok.

1. With the r299 I have saved as EXR by the QT interface without problems.

I have test to render from the console without the export script : exporting XML and render on console (yafaray-xml). The EXR picture has been saved normaly.

2. This is the Console messages.

rendering 2 passes, min 5 samples, 3 per additional pass (max 8 total)
[################################################################] (done)
imageFilm_t::nextPass: resampling 5766 pixels!
[################################################################] (done)
overall rendertime: 46.0859s
flushing imageFilm buffer
render settings
Yaf(a)Ray (302)    render time: 46.09s    
AA passes: 2, AA samples: 5/3 (mitchell)   Raydepth: 2 Shadowdepth: 2
Lighting:  GI: photons (100000), bounces: 9 with backgroundfinished, setting pixmap
flushing imageFilm buffer
render settings
Yaf(a)Ray (302)    render time: 46.09s    
AA passes: 2, AA samples: 5/3 (mitchell)   Raydepth: 2 Shadowdepth: 2
Erreur de segmentation

Erreur de segmentation = Seg fault

 

I'm french, so if you have difficult to understand I will ask someone helping me to write the description of bug.


—

Bjo,
[url=http://www.photon-3d.com]w w w . p h o t o n - 3 d . c o m[/url]

Fri, 17/07/2009 - 02:25 — DarkTide

#3

Component:Qt GUI» Code
Priority:normal» minor
Assigned to:Anonymous» DarkTide
Status:active» needs review

Please confirm if this is still a bug on latest RC3 if it is please provide more information, like the full console output not just a fragment

—

Just Vampires Playing To Be Mortals...
[color=#004000][b]---------{--<[/b][/color][color=#FF0000][b]@[/b][/color]

Wed, 16/09/2009 - 21:18 — _Mo_

#4

I have the same exact problem. When saving the scene to an XML and then rendering from the command line, it succesfully saves to EXR. But when trying to save it from the gui it crashes everytime with a segfault, without any other output (I run Blender with -d option). Other formats work ok.

My specs:

- Ubuntu 8.10 64 bit

- Blender 2.49a (precompiled binaries)

- YafaRay 348M (compiled from source)

—

Linux Mint DE 64bit | Blender 2.6 | Yafaray 0.1.2 beta, [url=http://www.matejmo.deviantart.com]matejmo.deviantart[/url]

Fri, 06/11/2009 - 04:24 — AndyBorrell

#5

Version:<none>» 0.1.1

I had the same problem too. With:

Yafaray = 432

Blender = 2.49b (precompiled binaries)

Suse 11.0

However, I've worked out what the problem was, and I have a solution.

 

This is the top of a gdb backtrace from the segmentation fault:

#0  0x08fa7bc0 in Imf::Header::operator= ()
#1  0x08fb102e in Imf::OutputFile::initialize ()
#2  0xb1ea6f4a in OutputFile (this=0xbfb4ebdc,
    fileName=0xa48f42c "/tmp/fdfds.exr", header=@0xbfb4eb74, numThreads=0)
    at ImfOutputFile.cpp:660
#3  0xb200ce94 in yafaray::saveEXR () from /usr/local/lib/libyafaraycore.so
#4  0xb200d1e3 in yafaray::outEXR_t::SaveEXR ()
   from /usr/local/lib/libyafaraycore.so
#5  0xb2ad2ded in yafaray::outEXR_t::flush ()
   from /usr/local/lib/libyafarayqt.so
#6  0xb1ff0c71 in yafaray::imageFilm_t::flush ()
   from /usr/local/lib/libyafaraycore.so
#7  0xb2d79a05 in yafaray::yafrayInterface_t::getRenderedImage ()
   from /usr/local/lib/libyafarayplugin.so
#8  0xb2ad1d54 in MainWindow::saveDlg () from /usr/local/lib/libyafarayqt.so

(I built the OpenEXR library with debug information first.)

It says that frame #2 is at ImfOutputFile.cpp:660. This is part of OpenEXR source code. The code at this line calls Imf::OutputFile::initialize.

Frame #1 says its at Imf::OutputFile::initialize as you'd expect, but PC value is massively different from the PC value at frame #2, despite supposedly being part of the same library (0x08fb102e compared with 0xb1ea6f4a). Gdb also hasn't picked up the debug information for these frames either. After probing gdb some more and running objdump on the blender binary I confirmed the following:

The precompiled blender binaries have the OpenEXR statically linked in. But yafaray links with the libraries dynamically, meaning that at runtime there are 2 copies of the OpenEXR library loaded. The libraries present on any given system might not be the same as those that were statically linked with Blender, and even if they were it would quite likely still not work anyway (among other potential problems, static data could remain unitialized in one of the loaded versions of the library).

 

Solution

The simple solution to this problem is to download the blender source and compile it yourself. The default configuration when building from source is to not statically link in the OpenEXR libraries (what you want). I have confirmed that this fixes the problem with the blender 2.49b source.

Tue, 16/02/2010 - 10:22 — heretic

#6

Version:0.1.1» 0.1.x

r521 still crashes on some exr

—

[url=http://www.Kunden-besser-informieren.de/]Kunden-besser-informieren.de[/url]

Images posted by me are solely posted for the purpose of the yafaray project. Any other commercial or non-commercial use, modification etc. of my images and its content requ

Tue, 16/03/2010 - 00:48 — heretic

#7

r543 now crashes regularly for me upon EXR-save

—

[url=http://www.Kunden-besser-informieren.de/]Kunden-besser-informieren.de[/url]

Images posted by me are solely posted for the purpose of the yafaray project. Any other commercial or non-commercial use, modification etc. of my images and its content requ

Mon, 22/03/2010 - 18:04 — heretic

#8

Problem is solved for me in current 538DT win32 build. On the msvc build tree it still exists for 54x+ on win32.

—

[url=http://www.Kunden-besser-informieren.de/]Kunden-besser-informieren.de[/url]

Images posted by me are solely posted for the purpose of the yafaray project. Any other commercial or non-commercial use, modification etc. of my images and its content requ