Hi,

After resolving my build problems earlier (-O3 in the CFLAGS caused
edje_cc to segfault while elementary was building, -O2 worked), i'm
now noticing extreme memory usage with Enlightenment. Not at first, it
gradually goes up over time.

I first noticed that after Enlightenment runs for a while, the machine
gets a bit "laggy" for want of a better description. Windows take a
while to respond when switching focus, clicks take longer to register,
stuttering while scrolling in Chrome... Wondering what was up, I ran
"top" just to see if some process had run away, and found this:

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
 8867 root      20   0  316872 128708  29988 S  26.1  1.6   1765:45 Xorg
17873 conrad    23   3 1627332 318176  84944 R  10.6  3.9   1876:52 chrome
 1174 conrad    23   3 1611356 555672 162412 S   5.9  6.9  80:20.43 chrome
20550 conrad    23   3 2926800 738060  49996 S   5.9  9.1 284:31.02 firefox
 9718 conrad    20   0 1975404 1.179g  86444 S   5.6 15.3 604:09.09
enlightenment
 3307 conrad    23   3 1225216 457652  69544 S   3.6  5.7  15:17.08 chrome
 ...

(That looked better with a mono-spaced font...)

The memory usage goes right back down again after selecting "Restart"
from the Enlightenment menu. This was much worse at first, after I
used the "-O2 -ffast-math -m=native" CFLAGS, going up to 4.5g under
RES overnight, the VIRT number had to be abbreviated with a 'g' as
well, and the %MEM value was over 50%!

While tracking down the previous build problem I tried with just "-O3"
and then just "-O2" to verify that was the cause of the previous
segfault, and that last build is the one that's currently running.
This seems to be using up memory at a slower rate.

I gave up trying to get the libraries freshly from git to build...
there were too many conflicting libwhatever-1.so -> 1.15.so / 1.16.so
conflicts, and some enlightenment modules were looking for
non-existent files in E20 vs E19 directories. Should i just wait for
the next release, or will i simply run into the same problems? Should
I ditch this new gcc 5.2.1? :) Is there any other way to track down /
solve this excessive memory usage?

Thanks,
-Conrad.

-- 
Whenever and  wherever you want.

------------------------------------------------------------------------------
_______________________________________________
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

Reply via email to