Solved jwm is insane?

[Aminavy]

Hello!
a few week ago jwm uses about 34MB of memory. I checked the "top" on yesterday and saw it used more than 120MB of memory!
Why?!!

output of top

CPU:  3.3% user,  0.0% nice,  1.0% system,  0.3% interrupt, 95.3% idle
Mem: 542M Active, 383M Inact, 22M Laundry, 832M Wired, 335M Buf, 1535M Free

  PID USERNAME    THR PRI NICE   SIZE    RES STATE    C   TIME    WCPU COMMAND
 1270 aminavy      20  22    0  2593M   269M select   1   0:36   6.54% firefox
 1257 aminavy     100  20    0    19G   581M select   2   2:19   4.88% firefox
 1039 aminavy      13  20    0   297M   137M select   3   0:30   1.46% Xorg
 1290 aminavy      20  20    0  2470M   179M select   3   0:11   0.00% firefox
 1042 aminavy       1  20    0   189M   126M select   1   0:03   0.00% jwm
 1267 aminavy      19  20    0  2469M   164M select   3   0:02   0.00% firefox
 1268 aminavy      19  20    0  2459M   154M select   2   0:01   0.00% firefox
 1298 aminavy      19  20    0  2443M   148M select   1   0:00   0.00% firefox
  901 root          1  20    0    13M  2204K select   0   0:00   0.00% powerd
 1309 aminavy      16  20    0  2438M   145M select   1   0:00   0.00% firefox

and in "ps" command:

aminavy 1042  0.0  3.7   194012 129380 v0  S    14:24   0:03.12 /usr/local/bin/jwm

 

[Alain De Vos]

Compare it to the memory usage of firefox or chromium ?

 

[YYY__]

A more reasonable answer here.

 

[Ogis]

Looks like a memory leak...

 

[Crivens]

Compare it to the memory usage of firefox or chromium ?

Just because those are obese memory hogs, that makes this any better?

 

[Aminavy]

Compare it to the memory usage of firefox or chromium ?

No.
with other window managers and itself (in post week)

Edit:
Oh! the problem was from background image...
Now it uses 26MB with smaller background image

 

[Crivens]

Edit:
Oh! the problem was from background image...
Now it uses 26MB with smaller background image

That reminds me of a time I had selected a hubble picture as a background. And logging in was sooo slow. (scaling 16k x 16k to screen resolution on 25MHz)

 

[YYY__]

It was planned.

 

[Ogis]

Now it uses 26MB with smaller background image

Still a lot...(here's my opinion)

 

[mer]

What about setting a solid background color? Lots of standard utilities to simply set the color.

 

[astyle]

which version of Firefox does OP have??? I've been struggling with v. 109 - on due to memory leaks, and nothing seemed to help, not even stuffing it into a jail and trying to limit the RAM via limits(1)... I had to switch to Chromium, it's better behaved on my hardware (Ideapad laptop with 8GB of RAM) in regards to memory leaks...

 

[Alain De Vos]

Note, my firefox is currently 102.11.0esr(64-bit). I must say Chromium is sometimes faster.
[But it's compile time is huge]

 

[Alexander88207]

Cant reproduce the issue from OP.

PID USERNAME    THR PRI NICE   SIZE    RES STATE    C   TIME    WCPU COMMAND
1701 Alexander8   53  20    0  1207M   254M piperd  10  15:33  35.20% wine.bin
1810 Alexander8  115  21    0  3243M   707M select   1   0:27   5.45% firefox
1709 Alexander8    1  21    0    26M    18M kqread   5   1:21   3.11% wineserv
1467 root          9  21    0   299M   142M select   8   0:18   2.23% Xorg
1818 Alexander8   29  21    0  2726M   337M select   3   0:05   1.94% firefox
1806 Alexander8    4  20    0   109M    63M select   2   0:02   1.75% xfce4-ta
1755 Alexander8   27  20    0  6899M   730M piperd   1   1:08   0.56% wine64.b
1731 Alexander8   23  20    0  1819M   318M piperd   0   0:12   0.38% wine64.b
1720 Alexander8    7  68    0  1712M    27M piperd   8   0:05   0.37% wine64.b
1824 Alexander8    5  68    0   115M    62M select   7   0:00   0.15% xfce4-te
1505 Alexander8    1  20    0    62M    29M select   2   0:01   0.04% jwm
1828 Alexander8    1  23    0    14M  3944K CPU3     3   0:00   0.04% top
1501 lightdm       4  20    0    34M  9848K select  10   0:00   0.01% at-spi2-
1630 Alexander8    4  20    0    34M  9628K select   5   0:00   0.01% at-spi2-

If that really should come from the background picture i wonder how big it was when i have already a big picture (6432x3620) as a background.

I do use graphics/feh in the jwm config to set the background btw.

 

[YYY__]

You have to load a wallpaper. It appears in the related thread link. There were two foreseeable options for the issue: additional build options or a heavy wallpaper.
The reading shows that it has already been solved.

EDIT:

If that really should come from the background picture i wonder how big it was when i have already a big picture (6432x3620) as a background.

PNG or JPG? (lossless data compression)
About feh... No tools are needed to load the background, just use .jwmrc:
<Desktop><Background type="image">/path/file.jpg</Background></Desktop>

 

[Alexander88207]

About feh... No tools are needed to load the background, just use .jwmrc:
<Desktop><Background type="image">/path/file.jpg</Background></Desktop>

Ehm, i think i keep using feh to set the background.

  PID USERNAME    THR PRI NICE   SIZE    RES STATE    C   TIME    WCPU COMMAND
 2021 root         10  20    0   293M   148M select   7   0:03  21.20% Xorg
 2079 Alexander8    4  21    0   118M    70M select   9   0:00   1.98% xfce4-te
 2083 Alexander8    1  20    0    14M  3916K CPU3     3   0:00   0.36% top
 2045 Alexander8    1  21    0   369M   268M select   2   0:01   0.13% jwm

 

[YYY__]

Which process is allocated the memory to feh?

 

[Alexander88207]

Which process is allocated the memory to feh?

To nothing, it places the image on the background and then exits.

 

[YYY__]

So think of the image being displayed on screen loaded infinitely from disk. Have you tried PNG too? Probably feh makes a difference. Try it with feh and jwmrc and share the memory usage for our understanding.

 

[Alexander88207]

I actually have found out that feh is not needed with my configuration.

I do use lightdm which loads already the background in the login and it stays in jwm.

 

[Alexander88207]

So this is now the usage if lightdm loads the image.

 

[YYY__]

Lightdm or parent process is adding the difference. I'm guessing someone who uses jwm to maximize resources wouldn't use lightdm, maybe not worth looking at memory usage.

 

[zirias@]

Ehm, i think i keep using feh to set the background.

  PID USERNAME    THR PRI NICE   SIZE    RES STATE    C   TIME    WCPU COMMAND
 2021 root         10  20    0   293M   148M select   7   0:03  21.20% Xorg
 2079 Alexander8    4  21    0   118M    70M select   9   0:00   1.98% xfce4-te
 2083 Alexander8    1  20    0    14M  3916K CPU3     3   0:00   0.36% top
 2045 Alexander8    1  21    0   369M   268M select   2   0:01   0.13% jwm

Hm, I don't see a reason why it should keep the pixmap after setting it for the root window. But maybe, this is just jemalloc being lazy? Does the behavior change when setting MALLOC_CONF=narenas:1,tcache:false,dirty_decay_ms:0,muzzy_decay_ms:0,abort_conf:true in its environment?

 

[Aminavy]

which version of Firefox does OP have??? I've been struggling with v. 109 - on due to memory leaks, and nothing seemed to help, not even stuffing it into a jail and trying to limit the RAM via limits(1)... I had to switch to Chromium, it's better behaved on my hardware (Ideapad laptop with 8GB of RAM) in regards to memory leaks...

firefox 113.

how much for you?

 

[astyle]

firefox 113.

how much for you?

FF 111 on my Ideapad... Info in this thread seems promising, I'm gonna try upgrading FF sometime soon and see if the memory behavior is any better since I last tackled that issue a few months ago.