Closed fletom closed 9 years ago
I can confirm this too, using livestreamer-curses
on Arch
Linux
Hey, it should be fixed in 09f03d4a0d4944e0dce85aa95e68e7cf0e2b237f. Thanks for the helpful report, I actually had that issue too and didn't really know where to look. A quick check with
ps -L -o pid= -p <pid> | wc -l
seems to show a thread count of 1 when not refreshing, could you check on your side ?
That command always outputs 3
on my machine. The threading count I was observing came from Activity Monitor app on my Mac (the equivalent of a task manager) and I'm not sure what the equivalent is on the command line.
I installed @09f03d4 and I can confirm that the thread count now stays low no matter how much I refresh the streams. I doubt I'll see thread.error
anymore but I'll let it run for longer and let you know if I do.
Thanks!
Ok! I'm preparing 1.5.0 and will release tomorrow if I don't hear from you by then.
It's been running all day without any threading errors. Definitely good for release. :)
I noticed that after a certain amount of time running in auto-refresh mode, the program always errors out:
Sure enough, watching my system process monitor, the process' active thread count increases by the number of streams every time the refresh is run. It would seem that the calls to check online status are spawned as threads but not released afterwards. It eventually goes up to 1,000s of threads and then refuses to spawn any more.