vasyliev89 created an issue (geany/geany#4321)
Title:
Warning: g_unix_open_pipe() called with FD_CLOEXEC; please migrate to using
O_CLOEXEC instead appears repeatedly when launching Geany, causing high CPU load
Description:
When launching Geany (version 2.0, GTK 3.24.41) on Ubuntu 24.04.2 LTS, the
following GLib debug messages appear repeatedly:
GLib DEBUG : g_unix_open_pipe() called with FD_CLOEXEC; please migrate to using
O_CLOEXEC instead
These messages flood the log output and correlate with a significant increase
in CPU usage by the Geany process. The application remains functional, but the
elevated CPU load can affect system responsiveness.
Disabling Geany’s built-in terminal removes the debug messages and returns CPU
usage to normal levels, indicating a strong link between the embedded terminal
and the repeated warnings.
Steps to reproduce:
Launch Geany with the built-in terminal enabled.
Observe the CPU load increase and repeated GLib debug messages in the logs.
Disable the embedded terminal and restart Geany.
Notice that CPU usage returns to normal and debug messages stop.
Expected behavior:
The code should use modern APIs (such as g_unix_open_pipe2() with
O_CLOEXEC) to avoid these debug warnings.
CPU usage should remain low during normal use of the built-in terminal.
Actual behavior:
Repeated GLib debug warnings about g_unix_open_pipe() usage with FD_CLOEXEC.
High CPU load correlated with these messages when the embedded terminal is
enabled.
Additional information:
OS: Ubuntu 24.04.2 LTS
Geany version: 2.0
GTK version: 3.24.41
GLib version: 2.80.0
Suggestions:
Review and update code using g_unix_open_pipe() to migrate to
g_unix_open_pipe2() with O_CLOEXEC.
Investigate if the embedded terminal integration is causing excessive repeated
calls.
If this originates from a library dependency, consider reporting upstream to
GLib.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/4321
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/[email protected]>
