ERR<2793>:eina_cow /home/antognolli/efl/dev/git/efl/src/lib/eina/eina_cow.c:385 eina_cow_write() Request writing on an pointer that is already in a writing process 0x63675b8

==2793== Invalid read of size 8
==2793==    at 0x50B6160: _image_data_get (evas_object_image.c:1547)
==2793==    by 0x57880D1: _eo_op_internal (eo.c:363)
==2793==    by 0x578825A: _eo_dov_internal (eo.c:403)
==2793==    by 0x57884F8: eo_do_internal (eo.c:434)
==2793==    by 0x50B5D96: evas_object_image_data_get (evas_object_image.c:1486)
==2793==    by 0x4013B0: _on_keydown (evas-images3.c:109)
==2793==    by 0x5096BD4: evas_object_event_callback_call (evas_callbacks.c:357)
==2793==    by 0x50A51B5: _canvas_event_feed_key_down (evas_events.c:2718)
==2793==    by 0x57880D1: _eo_op_internal (eo.c:363)
==2793==    by 0x578825A: _eo_dov_internal (eo.c:403)
==2793==    by 0x57884F8: eo_do_internal (eo.c:434)
==2793==    by 0x50A4AED: evas_event_feed_key_down (evas_events.c:2620)
==2793==  Address 0x40 is not stack'd, malloc'd or (recently) free'd
==2793== 
==2793== 
==2793== Process terminating with default action of signal 11 (SIGSEGV)
==2793==  Access not within mapped region at address 0x40
==2793==    at 0x50B6160: _image_data_get (evas_object_image.c:1547)
==2793==    by 0x57880D1: _eo_op_internal (eo.c:363)
==2793==    by 0x578825A: _eo_dov_internal (eo.c:403)
==2793==    by 0x57884F8: eo_do_internal (eo.c:434)
==2793==    by 0x50B5D96: evas_object_image_data_get (evas_object_image.c:1486)
==2793==    by 0x4013B0: _on_keydown (evas-images3.c:109)
==2793==    by 0x5096BD4: evas_object_event_callback_call (evas_callbacks.c:357)
==2793==    by 0x50A51B5: _canvas_event_feed_key_down (evas_events.c:2718)
==2793==    by 0x57880D1: _eo_op_internal (eo.c:363)
==2793==    by 0x578825A: _eo_dov_internal (eo.c:403)
==2793==    by 0x57884F8: eo_do_internal (eo.c:434)
==2793==    by 0x50A4AED: evas_event_feed_key_down (evas_events.c:2620)
==2793==  If you believe this happened as a result of a stack
==2793==  overflow in your program's main thread (unlikely but
==2793==  possible), you can try to increase the size of the
==2793==  main thread stack using the --main-stacksize= flag.
==2793==  The main thread stack size used in this run was 8388608.
==2793== 
==2793== HEAP SUMMARY:
==2793==     in use at exit: 1,006,804 bytes in 3,915 blocks
==2793==   total heap usage: 5,740 allocs, 1,825 frees, 1,637,448 bytes allocated
==2793== 
==2793== LEAK SUMMARY:
==2793==    definitely lost: 0 bytes in 0 blocks
==2793==    indirectly lost: 0 bytes in 0 blocks
==2793==      possibly lost: 320 bytes in 1 blocks
==2793==    still reachable: 1,006,484 bytes in 3,914 blocks
==2793==         suppressed: 0 bytes in 0 blocks
==2793== Rerun with --leak-check=full to see details of leaked memory
==2793== 
==2793== For counts of detected and suppressed errors, rerun with: -v
==2793== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 3 from 3)
Killed