On Mon, Apr 29, 2013 at 7:28 AM, Christopher Michael
<cp.mich...@samsung.com> wrote:
> On 27/04/13 10:42, Chris Michael wrote:
>>
>> On 26/04/13 16:51, Rafael Antognolli wrote:
>>>
>>> Hey devilhorns,
>>>
>>> On Fri, Apr 26, 2013 at 3:23 AM, Chris Michael - Enlightenment Git
>>> <no-re...@enlightenment.org> wrote:
>>>>
>>>> devilhorns pushed a commit to branch master.
>>>>
>>>> commit 8235272ec053eb4bfcb040d7c9c20b61c55ffb61
>>>> Author: Chris Michael <cp.mich...@samsung.com>
>>>> Date: Thu Apr 25 14:14:20 2013 +0100
>>>>
>>>> Reenable ability for async render of shm engine.
>>>>
>>>> Signed-off-by: Chris Michael <cp.mich...@samsung.com>
>>>> ---
>>>> src/modules/ecore_evas/engines/wayland/ecore_evas_wayland_shm.c | 8
>>>> ++++----
>>>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>>>
>>>> diff --git
>>>> a/src/modules/ecore_evas/engines/wayland/ecore_evas_wayland_shm.c
>>>> b/src/modules/ecore_evas/engines/wayland/ecore_evas_wayland_shm.c
>>>> index 31adbd7..82f5192 100644
>>>> --- a/src/modules/ecore_evas/engines/wayland/ecore_evas_wayland_shm.c
>>>> +++ b/src/modules/ecore_evas/engines/wayland/ecore_evas_wayland_shm.c
>>>> @@ -155,10 +155,10 @@ ecore_evas_wayland_shm_new_internal(const char
>>>> *disp_name, unsigned int parent,
>>>> ee->prop.draw_frame = frame;
>>>> ee->alpha = EINA_FALSE;
>>>>
>>>> - /* if (getenv("ECORE_EVAS_FORCE_SYNC_RENDER")) */
>>>> - ee->can_async_render = 0;
>>>> - /* else */
>>>> - /* ee->can_async_render = 1; */
>>>> + if (getenv("ECORE_EVAS_FORCE_SYNC_RENDER"))
>>>> + ee->can_async_render = 0;
>>>> + else
>>>> + ee->can_async_render = 1;
>>>
>>> I just tried this now, and it seems to work without those freezing
>>> issues. Have you fixed this recently, or did they disappear magically?
>>> If you fixed them, good work :)
>>>
>>> But I'm still seeing issues when using this async render. It seems to
>>> be segfaulting when exiting the application while things are still
>>> rendering. Can you take a look at this? If not, then maybe we would be
>>> better to not enable it by default until we know that it's working
>>> without bugs. What you think about it?
>>
>>
>> Yea, I got that once in a while myself. I would do (on average) 10 runs,
>> 9 would be ok, the last one would crash on exit. It's a strange issue :(
>> I started looking into it, but have not had time to finish.
>>
>> dh
>>
>>
>
> Spent some more time looking into this. Oddly enough, Terminology (when
> using the wayland_shm engine) does NOT segfault with async render enabled.
> It seems it is only elementary_test which is doing it ... tho I am still NO
> closer as to WHY it (randomly) happens :( Both valgrind and gdb were no help
> :(
:(
OK, I'll see if I can debug it this week, but have to take care of
some other bugs before that.
But from a quick look, I believe that it crashed while executing some
rendering callbacks after some things were already destroyed, like
Evas or something else on exit.
--
Rafael Antognolli
http://antognolli.org/
------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
