Crest [fork]

Your rating: None Average: 5 (10 votes)

Crest is a 'top' like application. Forked from


Attention SFOS 4.x users:

In their infinite wisdom, Jolla decided to ditch the procps package (which provides ps) and switch to the more limited busybox ps. That breaks Crest bigtime.

As of version 1.7.2, the Crest installation will replace busybox-symlinks-procps with procps-ng because of this.


Filtered processes


The default view is apps only. But what defines an app? Crest simple used to filter names like "harbour-", "jolla-" or processes with dots. Lighthouse also has an app view, but filters app names found in /usr/share/applications.
Crest now also matches the desktop files in /usr/share/applications, but also includes sailfish-qml apps/processes (which seems more accurate than the old method Crest used).

In "Show all processes" mode Crest does not show the processes that appear between brackets; processes that do not have an associated command line (mostly kernel threads and some system services). They do not display memory usage, but can use CPU power. Not showing these processes shortens the process list a lot.

If "Incl. no cmdline [top 60]" is actived, those processes are also shown. To shorten the list and prevent higher cpu load, the list is limited to the first 60 entries.


Crest shows the resident set size (RSS). It is less accurate than proportional set size (PSS), as PSS handles used shared memory use better. The downsize of PSS is that you need to have privileged access to collect that info.

Colors used for procesname

nemo/defaultuser = Theme.secondaryColor
root = Theme.primaryColor
others (Android?) = Theme.secondaryHighlightColor

License to kill

Running as nemo/defaultuser, you can only kill your own processes.
But when /usr/bin/sudo is located and does not ask for a password, it will use that when needed (assuming sudo is configured correctly, else it fails of course), so root and android processes can be terminated as well. Needless to say killing random processes can make your system unstable or even crash.


Sources on github

Application versions: 
File harbour-crest-1.4-1.armv7hl.rpm93.7 KB25/04/2020 - 16:15
File harbour-crest-1.4-1.i486.rpm104.94 KB25/04/2020 - 16:15
File harbour-crest-1.5-1.armv7hl.rpm101.84 KB18/05/2020 - 13:51
File harbour-crest-1.5-1.i486.rpm117.91 KB18/05/2020 - 13:51
File harbour-crest-1.6-1.armv7hl.rpm102.23 KB25/06/2020 - 21:40
File harbour-crest-1.6-1.i486.rpm118.63 KB25/06/2020 - 21:40
File harbour-crest-1.7-1.armv7hl.rpm102.3 KB28/07/2020 - 21:16
File harbour-crest-1.7-1.i486.rpm119.18 KB28/07/2020 - 21:16
File harbour-crest-1.7-2.armv7hl.rpm102.39 KB10/03/2021 - 20:21
File harbour-crest-1.7-2.i486.rpm119.13 KB10/03/2021 - 20:21
File harbour-crest-1.7-2.aarch64.rpm109.29 KB10/03/2021 - 20:21
File harbour-crest-1.7-3.i486.rpm119.46 KB09/10/2021 - 12:12
File harbour-crest-1.7-3.aarch64.rpm109.41 KB09/10/2021 - 12:12
File harbour-crest-1.7-3.armv7hl.rpm102.48 KB09/10/2021 - 12:12
  • 1.7-3 kill child processes after 2 seconds as a workaround for possible SFOS 4.2 hang issues
  • 1.7-2
    • replace busybox-symlinks-procps with procps-ng during installation
    • added aarch64 build
  • 1.7-1 Cover improvements:
    • do not update when inactive
    • added uptime in day/hours/minutes/seconds format
    • Some layout changes
  • 1.6-1 Added viewmode including no command processes
  • 1.5-1
    • Added remorse timer for process killing
    • Additional process detail page
  • 1.4-1
    • Added process search function
    • Do not show program path in portrait mode
    • Use colorscheme for various users
    • Sudo support
    • Dropped reversed sort ordering
    • Show pid in kill dialog
    • Change app detection


JacekJagosz's picture

Thank you so much for making it working agan, this is such a nice task manager!

JacekJagosz's picture

@ade Crest doesn't work for me either. I think it could be because I removed busybox-symlinks-bash and installed gnu-bash so patchmanager could work.
Could that be the source of the issue?

ade's picture

In case the 'ps' command does not finish it should now be terminated after 2 seconds to prevent this process causing a lock.

Still don't know what causes 'ps' to stall in some rare cases in SFOS 4.2, can't reproduce it from the commandline. Only thing I can think of is some kind of /proc/<pid> corruption.

If starting still does not work please reset the phone first to get rid of some previous 'ps' process or Crest instance. Or kill those manually. You can't use Crest for that at that moment ;-)

ade's picture

No, I don't think there is a relationship. It seems related, as I also seem to get no response every now and then when starting the app.
What I noticed is that the 'ps' command does not finish, so Crest can't continue. I have not found the exact cause of this, but I do have Crest running fine atm, with a small, non related change it seems.
I will see if it keep running ok and might upload that version.

NGC_Ollie's picture

On Crest is not starting anymore. No messages on commandline

ade's picture

It's still working here on 4.2.
Could it be that there is still some instance running in the background? Could you try a reboot first and if it does not help a reinstall of Crest?
If the problem still persists after that we will have to dig deeper.

pasik2's picture

After installing Android app support to my Xperia 10 II, Crest won't open anymore. Terminal output says:
[D] unknown 0 -Using Wayland-EGL
Library "" not found
Library "" not found

ade's picture

Can't say much about this as I do not have a 64bit SFOS version. Are those "not found" messages maybe just warnings that also pop up with other apps? And I do not see a direct link between Crest and Aliendalvik library files. There is no clear coredump/crash message? Is Crest the only app with issues after installing Android Support? Can other AArch64 users confirm this issue?

kraemera's picture

Ok, thanks.

kraemera's picture

Does not show the apps under Sailfish 4.0

ade's picture

Why don't you read the description first?

TMavica's picture

Thats ok now. I also can use sudo mode, Thanks

TMavica's picture

Yes. I just hold in all /app only process page, the percentage wont change, the original old version is keep changing in %

ade's picture

Xperia XA, Jolla Phone, Jolla tablet, all work as expected here when talking about process refresh.

You are aware that the pulley text does not say the current state, but the state in will be in once selected? That's a bit different from the older version.

If you are still convinced you have an issue I can only ask if you see error messages when starting from the terminal and if so, paste them here.

TMavica's picture

I set auto.refresh on, the page still not refresh itself. Also how to use sudo mode in it?

ade's picture

If not much is happening regarding processes, it might look not being refreshed perhaps?

I mentioned only the basics for using sudo with the idea in mind "people who are not familiar with sudo perhaps also should not use this feature".

TMavica's picture

It seem autorrefresh on is not working

ade's picture

Works as expected here: choosing "Autorefresh off" turns off refesh, selecting "Autorefresh on" from the pulley starts autorefresh once again.