Wire starts a process in the background consuming almost 100% of CPU core (/proc/self/exe) #8975
Description
It happens on all three computers running Ubuntu 24.04. When I start Wire, several new processes appear in the background. All of them are wire-desktop, but most of them were executed as '/proc/self/exe ...', and one of them is consuming almost 100% of one CPU core. Here is the listing of the command "ps -o pid,comm,args $(pgrep wire-desktop)":
PID COMMAND COMMAND
7688 wire-desktop wire-desktop
7691 wire-desktop /opt/Wire/wire-desktop --type=zygote --no-zygote-sandbox
7693 wire-desktop /opt/Wire/wire-desktop --type=zygote
7695 wire-desktop /opt/Wire/wire-desktop --type=zygote
7736 wire-desktop /opt/Wire/wire-desktop --type=zygote --no-zygote-sandbox
7762 wire-desktop /proc/self/exe --type=utility --utility-sub-type=network.mojom.NetworkService --lang=en-US --service-sandbox-type=none --enable-crash-reporter=e1016d25-7903-4f09-9776-e1d6b2d4fcb6,no_channel --user-data-dir=/home/vikturek/.config/Wire --shared-files=v8_context_snapshot_data:100 --field-trial-handle=3,i,2781258762904124591,14325748386761630632,262144 --enable-features=PdfUseShowSaveFilePicker --disable-features=SpareRendererForSitePerProcess,WebRtcHideLocalIpsWithMdns --variations-seed-version
7793 wire-desktop /proc/self/exe --type=renderer --enable-crash-reporter=e1016d25-7903-4f09-9776-e1d6b2d4fcb6,no_channel --user-data-dir=/home/vikturek/.config/Wire --app-path=/opt/Wire/resources/app.asar --no-sandbox --no-zygote --disable-gpu-compositing --lang=en-US --num-raster-threads=4 --enable-main-frame-before-activation --renderer-client-id=4 --time-ticks-at-unix-epoch=-1754133953149780 --launch-time-ticks=748199701 --shared-files=v8_context_snapshot_data:100 --field-trial-handle=3,i,2781258762904124591,14325748386761630632,262144 --enable-features=PdfUseShowSaveFilePicker --disable-features=SpareRendererForSitePerProcess,WebRtcHideLocalIpsWithMdns --variations-seed-version
7854 wire-desktop /proc/self/exe --type=renderer --enable-crash-reporter=e1016d25-7903-4f09-9776-e1d6b2d4fcb6,no_channel --user-data-dir=/home/vikturek/.config/Wire --app-path=/opt/Wire/resources/app.asar --no-sandbox --no-zygote --enable-blink-features --disable-blink-features --disable-gpu-compositing --lang=en-US --num-raster-threads=4 --enable-main-frame-before-activation --renderer-client-id=9 --time-ticks-at-unix-epoch=-1754133953149780 --launch-time-ticks=748852944 --shared-files=v8_context_snapshot_data:100 --field-trial-handle=3,i,2781258762904124591,14325748386761630632,262144 --enable-features=PdfUseShowSaveFilePicker --disable-features=SpareRendererForSitePerProcess,WebRtcHideLocalIpsWithMdns --variations-seed-version
7855 wire-desktop /proc/self/exe --type=renderer --enable-crash-reporter=e1016d25-7903-4f09-9776-e1d6b2d4fcb6,no_channel --user-data-dir=/home/vikturek/.config/Wire --app-path=/opt/Wire/resources/app.asar --no-sandbox --no-zygote --enable-blink-features --disable-blink-features --disable-gpu-compositing --lang=en-US --num-raster-threads=4 --enable-main-frame-before-activation --renderer-client-id=10 --time-ticks-at-unix-epoch=-1754133953149780 --launch-time-ticks=748860982 --shared-files=v8_context_snapshot_data:100 --field-trial-handle=3,i,2781258762904124591,14325748386761630632,262144 --enable-features=PdfUseShowSaveFilePicker --disable-features=SpareRendererForSitePerProcess,WebRtcHideLocalIpsWithMdns --variations-seed-version
7904 wire-desktop /proc/self/exe --type=utility --utility-sub-type=audio.mojom.AudioService --lang=en-US --service-sandbox-type=none --enable-crash-reporter=e1016d25-7903-4f09-9776-e1d6b2d4fcb6,no_channel --user-data-dir=/home/vikturek/.config/Wire --shared-files=v8_context_snapshot_data:100 --field-trial-handle=3,i,2781258762904124591,14325748386761630632,262144 --enable-features=PdfUseShowSaveFilePicker --disable-features=SpareRendererForSitePerProcess,WebRtcHideLocalIpsWithMdns --variations-seed-version
7947 wire-desktop /opt/Wire/wire-desktop --type=zygote
The process with pid 7854 is the one consuming the CPU. I can also provide some system details, but I am not sure, which information is relevant to this issue.