Arch Linux

nurverek

Member

Registered: 2021-03-29

Posts: 3

[SOLVED] efreetd always running at background locking 1 core to 100%

Hello,

The efreetd_icon_cache_create seems to be running almost always in the background, locking at least 1 core to 100%, it's been going on for quite some time actually and it doesn't seem to go away.

I've tried to look into the process, but there is no man page, the /usr/bin/efreetd is binary so idk how to understand why it does what it does...searched online but found very little useful info about this...
Tried removing the .cache/efreet/ manually no avail.

Here's system log which contains some errors :

Mar 29 12:39:59 nurverek gsd-media-keys[19957]: ERR<19957>:efreet_cache ../src/lib/efreet/efreet_cache.c:432 efreet_cache_shutdown() This application has not properly closed all its desktop references!
Mar 29 12:39:59 nurverek gsd-media-keys[19957]: /usr/lib/libefreet.so.1         0x7f8467d13643 0x7f8467cfa000
Mar 29 12:39:59 nurverek gsd-media-keys[19957]: /usr/lib/libefreet.so.1         0x7f8467d014ea 0x7f8467cfa000

I am currently using GNOME on Xorg, with kernel 5.10.26. and the Icons in use is Numix-Circle, tried different icons as well but same results. processor is i7 6700K@4.2 GHz

I've tried using several desktop environments and the issue seems to happen mostly on GNOME and Budgie.

I understand that the icon cache creation is a thing that has to happen but the process keeps going on for minutes at a time (sometimes 15 straight minutes) and then stops, only to restart few minutes after. Same thing happens on my laptop with same environment, and in there I actually start to run out of memory and laptop starts swapping (sometimes eventually crashing) since it's an old laptop with 4 GB of memory.

My question is, is this normal behavior? Is there a way to mitigate or minimize this to a more efficient version somehow...? it doesn't seem normal for an Icon cache process to run a core at 100% almost all the time. Often I notice it by the system having glitches and short hangups when I am going back and forth between windows and doing stuff.

htop : https://i.ibb.co/5Lm1PnW/Screenshot-fro … -39-57.png

Also I am new to Arch forums and this is my first ever post

Thanks.

Last edited by nurverek (2021-03-31 03:58:51)

nurverek

Member

Registered: 2021-03-29

Posts: 3

Re: [SOLVED] efreetd always running at background locking 1 core to 100%

Anyone?

CarbonChauvinist

Member

Registered: 2012-06-16

Posts: 413

Website

Re: [SOLVED] efreetd always running at background locking 1 core to 100%

Isn't efreetd part of the enlightenment DE and are you even using enlightment? If you're not using, perhaps try to remove enlightenment and its libraries completely?

Last edited by CarbonChauvinist (2021-03-30 11:57:22)

---

"the wind-blown way, wanna win? don't play"

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 15,351

Re: [SOLVED] efreetd always running at background locking 1 core to 100%

Welcome to archlinux forums.

$ pacman -F /usr/bin/efreetd /usr/lib/libefreet.so.1
usr/bin/efreetd is owned by community/efl 1.25.1-4
usr/lib/libefreet.so.1 is owned by community/efl 1.25.1-4
$ 

efl is only needed for 2 other packages : enlightenment & terminology .

https://wiki.archlinux.org/index.php/Enlightenment indicates enlightenment is a desktop environment / window manager .

Are you sure you need/want that package ?

If yes, maybe you can change options in etc/enlightenment/sysactions.conf or etc/enlightenment/system.conf .

P.S. please don't post big pictures, see
pasting pictures and code

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

nurverek

Member

Registered: 2021-03-29

Posts: 3

Re: [SOLVED] efreetd always running at background locking 1 core to 100%

Thanks for your replies.

You're right, terminology is my main terminal and is the package holds on to efl here.

Guess I have to get rid of terminology...shame. It's odd that terminology requires efl, I dont get it.

I was under the impression that icon caching just has to happen in this way. Now I feel dumb.

Also I apologize for the big picture, I have changed it into a link.

I have nuked terminology out of the system and it's all good now, I'll mark the post as solved.

Thanks