Spurious deadlocks after switching to C++11 mutexes/locks

[VizDock]

Hi
Issue almost identical to #1302
I followed advice from there trying to solve it with driver updating but didn't helped.
Since I keep all my git clones archived so that I can go back if something goes wrong, this minisatip15 is OK. 16 and 17 not ok

If I can see exact version in some file from cloned git, let me know.

As I wrote in #1302 OS starts acting weird, it takes alot of time to reboot and after reboot it goes to recovery mode. I just reboot it again and it starts up normally.
It made sense that it's driver issue but as it turns out, it is not.

I just started it with logging on latest version and when it hangs I will attach logs.

[VizDock]

here is log

minisatip.zip

Not even unencrypted local DVB-T channels work after it gets stuck

[Jalle19]

If I can see exact version in some file from cloned git, let me know.

If you run minisatip --version it will print the version.

it takes alot of time to reboot and after reboot it goes to recovery mode.

I have a hard time believing this is due to something in minisatip, especially if your computer boots into rescue mode after you
reboot.

You can skip ca from -l, it logs a ton of stuff. Need to fix that at some point so logs are more usable.

[VizDock]

It doesn't always go to recovery mode. If I issue reboot while minisatip is running then most of the time goes into recovery mode.
If I kill it before, then mostly it doesn't. But maybe it's not related at all, as you say..

Should I make new log without ca? Does this log tell you anything?
I just started minisatip version that works cos kids wants to watch cartoons on nickelodeon, but I can later make new log when they go to bed..

[Jalle19]

Yeah you can skip ca when making a log. Post the output of "dmesg | tail -n 50" too after it has gotten stuck.

[VizDock]

yesterdays testings showed that at some point only DVB-T stopped working, while DVB-S worked.
Today I restarted host, watched both DVB-S and DVB-T at same time, and it stucked after an hour or 2 of constant viewing same 2 channels.
Here is log.
I also recorded video to show you how long does it take to stop minisatip. Never had that before these last 2-3 versions. Usually minisatip stops instantly. And don't have this issue if I revert couple of commits back.

minisatip.log

2025-09-16.11-14-44.mp4

dmesg output is also attached

dmesg.txt

[Jalle19]

Thanks for the detailed explanation! Can you try #1310 ?

The reason minisatip takes long to exit is that is has deadlocked. The shutdown process stalls until systemd decides to kill it by force.

[VizDock]

OK compiled and started.. I'll let you know
thanks

[VizDock]

same thing happened.
I don't know if I did it correctly, I downloaded stream.cpp from your PR and after cloning repo I replaced original stream.cpp with this one.. and then compiled. If that's OK then same thing happened
Now I enabled logging again and restarted it to send you logs when it's stuck again.
Btw, I never looked before, but is this normal that minisatip consumes this much CPU?

[VizDock]

On second try when I added logging, after an hour system became unresponsive. Even logging in to ESX web interface took ages. Wife sent me video how it looks like on TV. It's DVBT FTA channel. Here are logs.

minisatip.zip

WhatsApp.Video.2025-09-16.at.6.41.29.PM.mp4

And after reboot:

[Jalle19]

No that's not normal, can you try to get a log next time this happens?

[VizDock]

This log in my last post is when it happened, just b4 I rebooted.. And ended up in rescue mode :)

[Jalle19]

@VizDock I pushed two more changes, can you please try again. Make a log while you're at it.