High CPU Usage After Reboot Until Service is Restarted

[xantrk]

What happened

Crowsnest Uses 30% CPU Until Service is Restarted

Whenever I reboot my mainsailOS raspberry Pi, I find CPU usage to around 30%. When I just restart crowsnest via UI or via systemctl restart crowsnest, it drops to just 1-2 percent. This causes my rPi to thermal throttle otherwise. Any ideas? High CPU usage sticks and persistent until service is restarted. No matter if it's idle, feed being active/inactive and regardsless of mjpeg or other codecs being used.

Fresh reboot:

After issuing systemctl restart crowsnest

#### crowsnest.conf
#### This is a typical default config.
#### Also used as default in mainsail / MainsailOS
#### See:
#### https://github.com/mainsail-crew/crowsnest/blob/master/README.md
#### for details to configure to your needs.


#####################################################################
####                                                            #####
####      Information about ports and according URL's           #####
####                                                            #####
#####################################################################
####                                                            #####
####    Port 8080 equals /webcam/?action=[stream/snapshot]      #####
####    Port 8081 equals /webcam2/?action=[stream/snapshot]     #####
####    Port 8082 equals /webcam3/?action=[stream/snapshot]     #####
####    Port 8083 equals /webcam4/?action=[stream/snapshot]     #####
####                                                            #####
####    Note: These ports are default for most Mainsail         #####
####    installations. To use any other port would involve      #####
####    changing the proxy configuration or using directly      #####
####    http://<ip>:<port>/?action=[stream/snapshot]            #####
####                                                            #####
#####################################################################
####    RTSP Stream URL: ( if enabled and supported )           #####
####    rtsp://<ip>:<rtsp_port>/stream.h264                     #####
#####################################################################


[crowsnest]
log_path: /home/furka/printer_data/logs/crowsnest.log
log_level: verbose                      # Valid Options are quiet/verbose/debug
delete_log: false                       # Deletes log on every restart, if set to true
no_proxy: false

[cam 1]
# mode: ustreamer                         # ustreamer - Provides mjpg and snapshots. (All devices)
mode: camera-streamer                                        # camera-streamer - Provides webrtc, mjpg and snapshots. (rpi + Raspi OS based only)
enable_rtsp: false                      # If camera-streamer is used, this enables also usage of an rtsp server
# enable_rtsp: true
rtsp_port: 8554                         # Set different ports for each device!
port: 8080                              # HTTP/MJPG Stream/Snapshot Port
device: /dev/video0                     # See Log for available ...
resolution: 1280x720                     # widthxheight format
max_fps: 20                             # If Hardware Supports this it will be forced, otherwise ignored/coerced.
#custom_flags:                          # You can run the Stream Services with custom flags.
# custom_flags: --format=YUYV
#v4l2ctl:                               # Add v4l2-ctl parameters to setup your camera, see Log what your cam is capable of.
v4l2ctl: sharpness=4,contrast=6

crowsnest (2).log

What did you expect to happen

Low CPU usage similar to after service manually restarted.

How to reproduce

Reboot host. (Raspberry Pi 3B)
Wait until mainsail boots
------ High CPU usage until service is restarted-----
...
..
Restart service
--Low/Normal CPU usage from this point onwards---

Additional information

No response

[mryel00]

Not reproducable on my end. Please join our Discord or the Discussions to further troubleshoot.

[github-actions]

Ahoi!

It looks like this ticket is a request for help (or similar).
Many helpful people will not see your message here and you are
unlikely to get a useful response.

We use the Github Issue-Tracker only for development related
topics, like feature requests, bug reports etc. To get help,
please join our Discord-Server or ask in Github Discussions:

• discord.gg/mainsail
• GitHub Discussions

This ticket will be automatically closed.

Fair wind and a following sea!
~ Your friendly MainsailGithubBot

PS: I'm just an automated script, not a real sailor.