You are not logged in.

#1 2025-07-15 20:22

Durhammer
Member
Registered: 2025-01-28
Posts: 230

Volumeicon size difference at startup versus manually starting[SOLVED]

This is most curious. My latest environment is using JWM, and the .jwmrc file's startup just has "volumeicon &" (used to have a -c config file option but no longer) and it comes up just fine and shows in my tint2 system tray.

When I look at what's running and their RAM sizes, I see volumeicon using 42+ MB RAM! That's quite a lot for such a simple purpose. But here's the really curious thing -- if I now make it exit and start a NEW one from the command line -- same command, "volumeicon &" -- the new instance uses a mere 11 MB RAM that's more like it!!! What's going on here, and how can I get the .jwmrc startup command so that it's like the manually-started command?

But hmmm.... Is this related? In my .jwmrc file, prior to instantiating volumeicon, I try starting pipewire. But pipewire doesn't show up in my ps_mem output. Another curious thing....

EDIT: Nope, has nothing to do with pipewire-start. I removed that and rebooted, and volumeicon still takes 42 MB. But now when I stop and re-start it manually, it's taking less than 10 MB.

EDIT 2: Okay, now this is really curious. Found out about another lightweight system tray volume control/mixer -- pnmixer -- and put that in place of volumeicon in the .jwmrc start code, and now THAT one is taking up over 43 MB at startup!!! It takes more RAM than volumeicon when stopped and manually started (12+ MB vs 10-ish), but that's probably due to extra features (mixer).

So it's not the application, it's when it's started that makes the difference. Any ideas?

Last edited by Durhammer (2025-07-19 15:16)

Offline

#2 2025-07-19 15:16

Durhammer
Member
Registered: 2025-01-28
Posts: 230

Re: Volumeicon size difference at startup versus manually starting[SOLVED]

Solving this, as it has nothing to do with volumeicon and maybe not even what's in JWM startup code. I just rebooted and fired up lxterminal to check ps_mem output, and lxterminal was showing as using some 50 MB! It's hardly ever over 20 MB. Sure enough, closed that lxterminal and started a new one, and now ps_mem shows it using just under 16 MB. Maybe an xorg thing?

Offline

Board footer

Powered by FluxBB