From 0c1eab0cf999db94164b70a80cc3941561a26844 Mon Sep 17 00:00:00 2001
From: "Carsten Haitzler (Rasterman)" <raster@rasterman.com>
Date: Tue, 9 Oct 2018 13:00:01 +0100
Subject: [PATCH] evas cache - avoid a segv...

but this needs mroe digging as to how this state was gotten to to
begin with.
---
 src/lib/evas/cache/evas_cache_image.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/lib/evas/cache/evas_cache_image.c b/src/lib/evas/cache/evas_cache_image.c
index c31be5b785..52447df9d0 100644
--- a/src/lib/evas/cache/evas_cache_image.c
+++ b/src/lib/evas/cache/evas_cache_image.c
@@ -348,7 +348,8 @@ _evas_cache_image_async_heavy(void *data)
    cache = current->cache;
 
    if ((!current->flags.loaded) &&
-       current->info.loader->threadable)
+       (current->info.loader) &&
+       (current->info.loader->threadable))
      {
         evas_module_task_register(evas_cache_image_cancelled, current);
         error = cache->func.load(current);