Firefox in KDE/Plasma->Resource problem

I have a firefox session with 5 windows and lots of open tabs. When starting it in an Icewm Desktop there is no problem. When starting it in KDE/Plasma there is a resource problem. I.e. starting another xterm will fail:

mk@linux-2kgy:~> xterm &
[2] 8374
mk@linux-2kgy:~> Maximum number of clients reachedMaximum number of clients reachedxterm: Xt error: Can't open display: :0


I’ve noticed that starting firefox in KDE/Plasma will launch additional kmozillahelper processes, which probably eat the resource. But which resource is it and can I change the limit for that resource somewhere ?
PS: Note that the error message also seems to need an additonal whitespace at its end.

I am seeing only one “kmozlllahelper” process.

If I login to Icewm, I see that there are 36 processes started.

I used

ps -fu $USER | wc -l

to check that.

If I login to KDE, then I see 63 processes started.

In both cases, that is checked without “firefox” running.

So yes, KDE starts more background processes than Icewm.

I’m not sure what is setting the limit for you – I’m guessing that’s a limit on X-clients. It possibly depends on the amount of memory.

The process is running after rebooting without opening any Mozilla app.

At one point I had 127 processes for kmozillahelper.

https://paste.opensuse.org/97209133

After installing kmozillahelper again, I see the processes growing again.

https://paste.opensuse.org/67488700

Here, I see only one “kmozillahelper” process (with Leap 15.2).

Right now the number is up to 27 on TW. :open_mouth:
Let me post this issue on KDE forum and see what happens.

Operating System: openSUSE Tumbleweed 20200923
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.74.0
Qt Version: 5.15.1
Kernel Version: 5.8.10-1-default
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-4810MQ CPU @ 2.80GHz
Memory: 31.0 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4600

I got nothing on the KDE forum. They don’t give me a warm and fuzzy feeling. :\

I guess I’ll email these 2 guys I see in yast software management under change log for kmozillahelper.

Tom Warnke <tom{at}toromtomtom{dot}com>

Fabian Vogt <fabian{at}ritter{dash}vogt{dot}de>

I had about 31 processes yesterday so I killed them all and I’ll see if they come back.

[FONT=Verdana]https://paste.opensuse.org/28824539

Operating System: openSUSE Tumbleweed 20200925
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.74.0
Qt Version: 5.15.1
Kernel Version: 5.8.10-1-default
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-4810MQ CPU @ 2.80GHz
Memory: 31.0 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4600[/FONT]

FYI…

Firefox is responsible for starting kmozillahelper, so this is most likely
an issue with Firefox. Please file a bug report on
https://bugzilla.opensuse.org/ and attach the journal of the relevant time
frame.

Thanks,
Fabian

Bug already opened…

https://bugzilla.opensuse.org/show_bug.cgi?id=1176852

Here’s an update for kmozillahelper on TW.

https://software.opensuse.org//download.html?project=home%3AVogtinator%3Aboo1176852&package=kmozillahelper

Hey mkossmann,

I would assume you’re also running Tumbleweed. Have you installed the update yet? It’s working fine for me 1 day later.

https://paste.opensuse.org/57340090