devilhorns pushed a commit to branch master.

commit da275a76b10880ac5a84acb61349a0c291567920
Author: Chris Michael <[email protected]>
Date:   Mon Aug 5 12:32:00 2013 +0100

    Check for Image_Entry being valid before calling evas_cache_image_drop.
    
    NB: Image_Entry passed in to this function Could be NULL (hence the
    previous if ie check above. Do not call evas_cache_image_drop on a
    NULL Image_Entry as evas_cache_image_drop does not validity checking.
    
    Signed-off-by: Chris Michael <[email protected]>
---
 src/lib/evas/cache/evas_cache_engine_image.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/lib/evas/cache/evas_cache_engine_image.c 
b/src/lib/evas/cache/evas_cache_engine_image.c
index eb39b36..5c6ae42 100644
--- a/src/lib/evas/cache/evas_cache_engine_image.c
+++ b/src/lib/evas/cache/evas_cache_engine_image.c
@@ -117,7 +117,7 @@ _evas_cache_engine_image_alloc(Evas_Cache_Engine_Image 
*cache,
    if (eim)
      evas_cache_engine_image_drop(eim);
    eina_stringshare_del(hkey);
-   evas_cache_image_drop(ie);
+   if (ie) evas_cache_image_drop(ie);
    return NULL;
 }
 

-- 

------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk

Reply via email to