zmu processes multiply when using RTSP2Web type MSE

Current Development version likely to have breaking changes
Post Reply
IgorA100
Posts: 203
Joined: Sat Feb 03, 2024 11:55 am

zmu processes multiply when using RTSP2Web type MSE

Post by IgorA100 »

I'm trying to make RTSP2Web type MSE work more correctly.
But I can't understand why ZMU processes multiply when the stream is restarted. WebSocket closes when the stream is stopped.
The number of ZMU processes is less than the number of stream restarts. Some ZMU processes consume a lot of CPU resources.
I can't understand why this happens and what is the pattern
This doesn't always happen, which blows my mind even more.
After refreshing the ZMU process page, things are back to normal for a while. Then it all repeats...
Attachments
1b.jpg
1b.jpg (168.81 KiB) Viewed 5932 times
1bb.jpg
1bb.jpg (248.58 KiB) Viewed 5932 times
1bbb.jpg
1bbb.jpg (206.54 KiB) Viewed 5932 times
IgorA100
Posts: 203
Joined: Sat Feb 03, 2024 11:55 am

Re: zmu processes multiply when using RTSP2Web type MSE

Post by IgorA100 »

I think I figured out the reason.
I didn't send the "CMD_STOP" command when stopping the thread. I thought it was enough to just close the socket.
I'll keep watching.
User avatar
iconnor
Posts: 3356
Joined: Fri Oct 29, 2010 1:43 am
Location: Toronto
Contact:

Re: zmu processes multiply when using RTSP2Web type MSE

Post by iconnor »

zmu is used to get the current monitor status (instead of zms since we aren't using zms).

They shouldn't linger. They should only exist for a moment.
IgorA100
Posts: 203
Joined: Sat Feb 03, 2024 11:55 am

Re: zmu processes multiply when using RTSP2Web type MSE

Post by IgorA100 »

iconnor wrote: Sun Feb 16, 2025 8:15 pm They shouldn't linger. They should only exist for a moment.
That's right. They don't stay for long, but there are a lot of such processes.
Many processes are called to one monitor at the same time (8 processes are visible in the screenshot) instead of one. Strange behavior.
The number of processes really doesn't increase if you call CMD_STOP.
Post Reply