[Bf-committers] Re: sequencer crash

Ton Roosendaal ton at blender.org
Thu Mar 9 23:23:47 CET 2006


Hi,

> Hi Toni,
>
>> with an exr sequence, i dont know what happens
>
> looks more like an openexr-crash than a sequencer-crash to me.
>
> Especially:
>
>> #15 0x084b7bf3 in ~FrameBuffer (this=0xbfccce20) at  
>> ImfFrameBuffer.h:120
>> #16 0x084b6db1 in imb_load_openexr (mem=0xb49bc000 "v/1\001\002",
>>     size=1601687, flags=1)
>>     at source/blender/imbuf/intern/openexr/openexr_api.cpp:656
>
> These lines are suspicious. Why does the code call the
> FrameBuffer-destructor on load (haven't dived into openexr-support,  
> maybe
> it's ok).

I have no idea either... not a c++ coder here. C++ seems to have a  
magical way of freeing memory.
Could you check the imb_load_openexr() call please? Maybe something  
stupid happens there...

-Ton-

>
> Greetings,
> Peter
>
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at projects.blender.org
> http://projects.blender.org/mailman/listinfo/bf-committers
>
>
------------------------------------------------------------------------ 
--
Ton Roosendaal  Blender Foundation ton at blender.org  
http://www.blender.org



More information about the Bf-committers mailing list