Hi Gustavo, On Tue, Oct 18, 2016 at 4:59 PM, Gustavo Sverzut Barbieri <barbi...@gmail.com> wrote: > Tried this fix for efl_net_server_example and it doesn't fix the > problem, instead it stops crashes but enters an infinite loop: > > ERR<17134>:ecore lib/ecore/efl_promise.c:301 _efl_loop_future_cancel() > Triggering cancel on an already fulfilled Efl.Future.
Can you try fb1feee480270c3e0e556774fc4ee613c82c7dba ? > since it's now expected that the promise will NULL-ify the pointer > once its done, this must be done earlier as well, otherwise my pd->job > (efl_io_copier.c) will still use that in its destructor. Yes and it really should. The problem with this is that I now need to fully override in all case weak ref. I think this is the last blow on using eo object for future, if I need to reimplement even the minimal set of feature as they don't match. I think I will move away from eo object before we freeze 1.19, but after we merge eo, ecore and efl interface. -- Cedric BAIL ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
