Re: [E-devel] null pointer in Image_Entry info

[Mikael L. <mik...@gm...>]

On Thu, Sep 24, 2009 at 5:19 AM, Mikael Liljeroth <
mik...@gm...> wrote:

> Hi, I have encountered a rather strange problem when testing revision 42549
> of the efl libraries.
> The problem seems to be related to images and the evas image loaders.
> I'm using a custom built evas engine that uses
> evas_common_load_image_from_file and then
> the evas_cache_image_load_data to load the image data in eng_image_load and
> eng_image_draw
> resp. My test application creates image objects and deletes them
> repeatedly.
>
> The problem is that I get a sigsegv when
> evas_common_load_rgba_image_data_from_file tries to
> call the loader function file_data. This happens because the info.loader in
> the Image_Entry is null.
> When the image module is loaded the info.loader is set correctly but
> somehow gets cleared on
> the way to eng_image_draw in the evas engine. This never happens for the
> first image, only for
> the second or later.
>

Correction: It does happen for the first image in some cases.


>
> Is it ok to use evas_common_load_image_from_file and
> evas_cache_image_load_data together
> or is there any other important function that must be called when loading
> an image in an evas engine?
> When eng_image_free is called I use evas_cache_image_drop.
>
> /Mikael
>