On Mon, 27 May 2013, Carsten Haitzler wrote:

> On Thu, 9 May 2013 10:42:30 -0700 (PDT) Bryan Olmstead <[email protected]>
> said:
>
>>
>> E has been freezing during reload/restart and theme update.  The problem
>> is that I cannot reproduce it 100% of the time.  It seems to happen during
>> two specific events:
>
> can i suggest one thing. dont copy the theme direct.. REPLACE. so dont do:
>
> cp theme.edj ~/.e/e/themes/theme.edj
>
> do:
>
> rm ~/.e/e/themes/theme.edj
> cp theme.edj ~/.e/e/themes/theme.edj
>
> this should help.

Thank you for the suggestion and explanation.  I'll definately do that and 
see if I can reproduce anything in e18.  If e18 does freeze will the 
crashdump file from e18 work?

Thanks,

-bryan

> basically by copying you are replacing an "in-use" file. its like copying a
> binary on top of one in use - or a shared lib. binaries map their contents
> direct from the file and this corrupts code in memory.
>
> now...admittedly edj files are DATA files..., they dont contain code, BUT e
> (edje) is continually paging/seeking data from that file whenever it needs it.
> it isn't all loaded once then never used again. this is how e manages to keep
> memory usage down - but only loading what is needed when it's needed then
> discarding it when it's no longer needed. edj files (eet files really) are
> designed specifically to be efficient/fast to random-access read data from
> anywhere inside of them for this purpose. so basically any edj file for any
> theme etc. anywhere - consider these files "in use" and deleting or modifying
> them will have consequences. if you want to replace them replace them by
> deleting first then copying there. existing mappings of the file will remain
> intact.
>
> now on our end... we shouldnt hang or crash if you go corrupting your edj
> files. we should maybe display some garbage, missing elements or whatever...
> but it shouldnt crash etc... but we need to find and fix these issues and we
> need to know how to reproduce it and we'll get a fix into our next release
> (s). :)
>
>> - I have been working on a theme and when it is recompiled and I copy it
>> to ~/.e/e/themes e will freeze right away, when I change desktops, try to
>> restart or during the restart.  It is not reproducable all the time (eg:
>> change an image, change the text color...).
>
> all i can ask is that at some point you upgrade to our git masters of efl and
> e and let us know if it still happens and if it does.. get us backtraces! :) 
> so
> we can fix for efl1.8 and/or e18. :)
>
>> - When moving a module on the desktop (sometimes just selecting it for
>> move/resize), then restarting e can freeze.  Sometimes this happens the
>> first time I move the module, sometimes I have to move more than one a
>> half-dozen times and restart, then repeat a half-dozen times.  This
>> example did include forecast and places, so I understand if it's not
>> applicable.
>
> hmm odd. i've never seen any such freeze in the past when i stuffed clocks and
> what not on my desktop for testing. if you can get a backtrace of when e is
> frozen... that'd be cool.
>
>> - When removing modules from the desktop e can freeze.  This example only
>> included default e modules.  The example crashdump had one clock on the
>> desktop and I was trying to remove a pager that did not appear, but was in
>> the modules list for the desktop.
>
> argh. the crashdump no longer is helpful as our code for comp has changed so
> much.... :( as above. does it still happen on git master?
>
>> In all of the examples, when e freezes the white warning box with the
>> option to restart or exit does not appear.  I have to hit
>> ctrl-alt-backspace to kill everything.
>>
>> When looking at the processes I found the .e-crashdump.txt file being
>> created so I recompiled e and the efl in debug, non-optimzed mode and have
>> the crashdump files for the freezes attached.
>>
>> I have e 0.17.2.1, efl 1.7.6 installed on slackware x86_64, 14.0.
>
> :/ :\ :S :D
>
> -- 
> ------------- Codito, ergo sum - "I code, therefore I am" --------------
> The Rasterman (Carsten Haitzler)    [email protected]
>

------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
_______________________________________________
enlightenment-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

Reply via email to