App Launching From GNOME Shell Now More Robust Under Memory Pressure & Faster
Written by Michael Larabel in GNOME on 22 June 2018 at 11:49 AM EDT. 31 Comments
GNOME --
Right now on systems with low amounts of available system memory, GNOME Shell can sometimes fail to launch applications due to an error over not being able to allocate memory in the fork process. With the latest rounds of Glib optimizations, this should no longer be the case.

Launching applications within GNOME Shell when under memory pressure can sometimes fail as right now it needlessly tries to clone the process virtual address space of the RAM-heavy GNOME Shell. Under optimization work merged yesterday to Glib by Endless Computers' Daniel Drake, the Glib gspawn code has been modified to make use of Glibc's posix_spawn() code with some changes and should avoid these "cannot allocate memory" errors.


It's also noted that this change to Glib gspawn should also provide a general speedup for launching of applications thanks to not having to clone the entire VM space.

The optimization work was merged in this patch among others merged to Glib on Thursday.

About The Author
Author picture

Michael Larabel is the principal author of Phoronix.com and founded the site in 2004 with a focus on enriching the Linux hardware experience. Michael has written more than 10,000 articles covering the state of Linux hardware support, Linux performance, graphics drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated benchmarking software. He can be followed via Twitter or contacted via MichaelLarabel.com.

Related GNOME News
Popular News This Week