Re: High CPU usage in GWorkspace but no clue

Hi Riccardo,
Hi Tim,

On 2025-10-28 14:36:40 +0100 Riccardo Mottola 
<[email protected]> wrote:

> Hi,
> 
> On 2025-06-28 22:51:28 +0000 Patrick Cardona <[email protected]> 
> wrote:
> 
>> I have tuned my environment, and I had no issues for several days, 
>> which is 
>> not saying it could not happen. See and wait... There are the three 
>> modifications I applied:
> 
> How are things with this? Ever happened again?
> 
> It did to me - I cannot have a certain way to reproduce it. I thought 
> it was 
> triggered by actions like renaming, but I was able to observe it 
> without. 
> Stupid things it always takes days.
> 
> Things that I guess might trigger are:
> - presence of the inspector, maybe only the content inspector and 
> changing/observing many files
> - switching between many directories, perhaps with inspector open
> - changes of files "under the hood" by other process (uncertain, most 
> often, 
> nothing happens)
> 
> The latter should affect more fswatcher, but maybe messages get 
> htrough? I 
> don't know.

Since I modified my .xinitrc / .xsession with some delays for tasks 
like Updater, I never saw again crashes nor untimely restarting of 
GWorkspace while using.

I have only, sometimes, at the very begining of the Xsession an alert:
"The FSWatcher connection died. Do you want to restart it?" I agree 
and then the whole session with long uptime seems ok.

My .xinitrc used within PiSiN thn within AGNoStep for several months:

#!/bin/sh

# $HOME/.xinitrc
### Xinit starts Xserver...
PID_XSESSION=$$

### Window Manager
/usr/bin/wmaker --no-dock --no-clip --static &
##########################################################
### See: $HOME/GNUstep/Library/WindowMaker/autostart
##########################################################

#################################################################
### Sourcing GNUstep environment:
### This is done with $HOME/.profile, not here.
#################################################################


sleep 1
/System/Tools/openapp SimpleAgenda &

### GWorkspace within a DBus session
sleep 2
exec dbus-launch --sh-syntax --exit-with-session /System/Tools/openapp 
GWorkspace

### This is a secure way in any case Dbus fails to kill the session:
kill $PID_XSESSION

And this is my autostart:

#!/bin/bash
#
# WindowMaker will wait until this script finishes, so if you run any
# commands that take long to execute (like a xterm), put a '&' in the
# end of the command line.
#
# This file must be executable.
#
xset m 20/10 4

### This is to prevent DMPS and blanking issues on RPI machine
xset -dpms
xset s off

### gdnc
gdomap -L GDNCServer || gdnc &

### compton: the -b arg means as a daemon like &
pgrep compton || compton -b

### Notifications
systemctl --user import-environment DISPLAY
pgrep dunst || dunst &
sleep 2 && /usr/local/bin/loading.sh &

### conky
pgrep conky || sleep 8 && conky -c ~/.config/agnostep/conky.conf &

### Updater
sleep 10 && /usr/local/bin/Updater -d &

### Birthday Notifier
sleep 10 && /usr/local/bin/BirthNotify &


Patrick

-- 
Patrick Cardona - Pi400 - GNU/Linux aarch64 (Debian 13.1)
Xorg (1:7.7+24) - libcairo2 (1.18.4-1+rpt1 arm64)
Window Maker (0.96.0) - GWorkspace (1.1.0 - 02 2025) - Theme: AGNOSTEP 
- MUA: GNUMail (1.4.0)