On Wed, 10 Jun 2020 11:29:45 -0400 Conrad Knight <iestynap...@gmail.com> said:
> Another data point: > I've noticed this error only occurs when E is started the first time > after the computer boots. If i log out and back in again without > rebooting it doesn't. I checked with the time stamp debug output i > added, and the time from setting the timer to clearing it is then 1s. > Down from 14s! Probably because everything is already in memory? yes. possibly. if you change it to 20 sec instead of 10 - does the problem go away? > On Wed, Jun 10, 2020 at 4:57 AM Carsten Haitzler <ras...@rasterman.com> wrote: > > as no one who reports > > the issues actually has provided detailed debug and analysis of what is > > going on. > > I can certainly add a few more debug print statements... As you > pointed out, setting the timer to a larger value would avoid the error > message, but if this would help figure out a faster startup i'd rather > do that. I just need to know where, and what output you'd like to see. well first want to confirm a longer timeout does work. as for why its slow... without actually profiling your machine... i cant say... it may be you have an absolute tonne of icon themes or icons or desktop files installed that simply cause so much disk io that ... it does take that long. i mean the scan could also possibly be faster. i could design something that as long as it makes forward progress it wont care how long it takes - it then need to keep reporting that its moving forward as it goes, not just when done, but both of these mean more of a "time to rewrite efreet" which is on my long todo list :) -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- Carsten Haitzler - ras...@rasterman.com _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
