@whpony96: The program do not really lock up, it just looks like that. Everything in the Windows UI is message-based. When you move your mouse, press a key or click somewhere different messages are generated for Windows applications. As long as you take care of these messages the application will act in a responsive way. But if you don't process that for 4 seconds or so, Windows will mark the application as "not responding" in the task manager, since it now assumes that the application may have run into problems. So, to keep the feeling of an application to "work as normal" as a developer you have to process those windows messages at all times as long as the application is running. All Windows applications and Windows itself has to do it, and I'd say that most Windows applications do that at all times, even if they are processing a lot of files, data, GPU or CPU time.
In this case it seems like Anystream stop checking for messages during muxing at the end, making the application look unresponsive, There are likely ways to mitigate it, but it all boils down to how the application is written and if it is prioritized enough to resolve it.
In this case it seems like Anystream stop checking for messages during muxing at the end, making the application look unresponsive, There are likely ways to mitigate it, but it all boils down to how the application is written and if it is prioritized enough to resolve it.