just for completeness, below is a bash script that uses lsw recursively
to walk the tree. it's a bit overkill (feeling guilty for having missed
the hackathon?). "once a Fortran programmer..."
#!/usr/bin/env bash
# this script walks the tree of known X windows on the system and
# prints out
s...@mailless.org wrote:
> or use lsw for a specific window:
>
> lsw | grep "some webpage title" | cut -f1 -d' ' | xargs xprop -id | grep PID
ah, thanks.
btw, i ran into a bug in, i assume, lsw.
bash minshall-apollo: {1339} lsw 0x164
Segmentation fault (core dumped)
at the time, x
or use lsw for a specific window:
lsw | grep "some webpage title" | cut -f1 -d' ' | xargs xprop -id | grep PID
S. Gilles,
> xprop | grep PID
yes, nice. i hadn't known. this
for i in $(xwininfo -children | tr '[:blank:]' \\n | grep '^0x'); do
xprop -id $i | grep PID;
done
i guess, gives me PIDs for all the windows in a tabbed set.
thanks! Greg
On 2017-09-06T07:14:21+0300, Greg Minshall wrote:
> hello.
>
> every now and then some browser instance goes resource wild. top(1) or
> ps(1) show the PID consuming all the resources (normally a webkit
> instance), but i haven't figured out a way to go from that to knowing
> which instance to kil
hello.
every now and then some browser instance goes resource wild. top(1) or
ps(1) show the PID consuming all the resources (normally a webkit
instance), but i haven't figured out a way to go from that to knowing
which instance to kill off, given that most often i start surf from
dwm(1), which s
