Summary: When loading a larger image, attempting to activate the viewer node in the UV Image pane results in a segmentation fault.
Version: SVN 26276
Platform: Linux amd64 (Ubuntu 9.10)
Reproduction: 1) Open a composite viewer node. 2) Create an image node. 3) Create a viewer node. 4) Make certain that a UV Image pane is open but that the viewer node is _NOT_ active. 5) Load a large image file - the samples attempted were 20 to 40 meg tiff files. 6) Briskly attempt to change the UV Image pane view to the viewport.
What will happen is that as the file loads, the preview image will appear in the input node. As the image preview node appears in the UV Image pane viewport node, Blender will generate a segmentation fault. It should also be noted that the same segmentation fault will not appear if the file loads entirely before flipping the UV Image pane. This is indicated by the preview appearing in the input node. If requested, sample TIFF can be supplied.
Description
Event Timeline
Hi, I've tried to recreate this but couldn't reproduce a crash in the compositor/image viewer specifically... It slows blender down a lot though, and i got a crash in a seemingly unrelated ui function (mem corruption..?)
is it possible for you at all to make a debug build and run blender in gdb to get a crash backtrace? I can help you in #blendercoders if you need a hand. It would make finding these crashes much easier.
cheers
Ok... so toggled BF_DEBUG and gdb the resultant Blender binary.
Unfortunately, after I try to run Blender, as soon as I get into the Compositor the system becomes completely unresponsive. The only way to get things back is to use a remote ssh to kill the Blender process or use SysRq k to kill everything.
It seems that it will randomly freeze somewhere during or after selecting the "Image" node. Sometimes it freezes up on the selection of the menu popup and sometimes it freezes up after clicking on the image file in question. gdb doesn't show anything relevant in the output from what I can see other than standard exits for threads.
Can you try this again on a recent SVN revision? Brecht fixed several bugs regarding threading/memory access in the compositor recently.
rev27899, ubuntu 9.10 32 bit, ati proprietary drivers
confirmed with a 230 Mb tiff file.
The segfault appeared while connecting the input node to the viewer, just after switching the UV region to 3D view (the preview of the picture was still not loaded)
http://www.pasteall.org/12105/c
this is strange, blender always signals metarig_demo.ogv prior to a libpng error on my system, don't remember to deal with such a file...
regards
Hi,
Troy I can't reproduce this here (Linux, Ubuntu 9.10 64 bits), is the bug there ?
can you try this again on the last svn revision ?
Marc I think you crash has nothing to do with what Troy report, you are in a 32 bits system try to load a 230 Mb file and malloc fail to allocate that much memory.
- Diego
Hi,
A couple of week and no update in the report, I can't reproduce this here so I assume it's fixed in the current svn, please if the bug is still there and you have the problem reopen the report.
Thanks,
- Diego