root@FuriPhoneFLX1s:~# ps aux|grep geoc
geoclue 3425 0.4 5.0 2159232 394600 ? Ssl Jan17 11:54 /usr/libexec/geoclue
Currently Geoclue has been running on my phone for just over 2 days (gnome-maps is open in the background which keeps geoclue running) and it allocated over 2G of RAm and has 394M resident which is excessive. In a previous run it allocated 4G exactly which appears to be some sort of hard coded limit to memory use and then the OOM killer started repeatedly killing programs. The fact that the OOM killer didn't kill Geoclue might be a bug in the OOM killer.
The first time I had this happen it took about 24 hours to get to 4G so this time it appears to be leaking memory more slowly.
Is there any better place to report software bugs than this forum?
etbe Topic starter
19/01/2026 4:19 pm
https://github.com/FuriLabs/issue-tracker/issues
Should I file an issue at the above URL for this?
https://github.com/FuriLabs/geoclue/
This URL has geoclue source for version 2.7.1-2 but the version on my phone is 2.7.1-3+furios6+git20250823000016.d49f5fb.forky.production and a quick look at the changelog shows there's a huge amount of changes. Is the source for 2.7.1-3+furios6+git20250823000016.d49f5fb.forky.production online somewhere? I'd like to try running valgrind but there's not much point without the source.
newts 28/01/2026 8:29 am
I had the same problem today. Uptime 4 days I noticed the low memory notification for Firefox but it looks like geoclue is the culprit. I killed the process but I haven't gone back to see if location still works or if geoclue respawned
etbe Topic starter
28/01/2026 3:42 pm
In the Furios configuration geoclue is spawned by a socket connection and terminates when connections end. So if you kill gnome-maps (or whatever is using GPS) then it should terminate. Just forgetting that an app is running in the background is common and we need the system to handle this.
