Continuing the discussion from “Topaz Video Ver 1.0.1 won’t close properly” (topic was merged in [RESOLVED 1.1.0] App Hangs on Exit recently):
I installed the newest version 1.2.1 just a few days ago. The linked poblem still occurs, unfortunatelly (5 months after it was reported in the linked issue).
Open the program and a file
Upscale with Starlight Mini (also happend with Proteus Natural recently. I haven’t tested any other models yet with the current version)
After the rendering is done: try to close the program (via “X” in the top corner or via File Menu) > the interface freeces (well, the user interface of the app disapperars, there is only an empty black/darkgrey window left, without any buttons)
The blank program window can only be forced to quit/close with the Taskmanager
I had a look at the logfiles but the crash/freeze is not listed at the end, the log files end with the sucessful finish of the rendering.
In a quick test I also deleted the project file so that a new project was created when the program was restarted > no change, still freeze when trying to close after a Starlight rendering
Not sure if relevant: Win11, 5080 16GB, current Nvidia StudioDriver 591.74 - I’m mostly working with files in MOV prores 422 hq format with 50fps
Thanks for the update on this issue, the devs are looking into this further, as it is a former issue that was resolved and has come back.
Previously, using the File>Exit option did work to close the app promptly instead of clicking the X in the top right corner, but both in some instances seem to be running into an issue at this time.
As soon as the devs are able to sort out a patch we will get it added in.
Thank you and thanks to the devs for looking into it!
The forum software states “This topic will close 2 months after the last reply” so I’ll add the versions where this issue isn’t resolved to keep this thread alive:
Topaz Video 1.3.0: not resolved.
The window freeze also happend after testing the new Gaia2 model. I guess it’s not related to the model that was used, maybe it is just a general “close app” bug.
The problem arises because the app crashes internally—that is, it gets caught in an infinite READ loop, repeatedly reading the very file it just wrote.
In addition to impairing the actual AI rendering performance by approximately 25 to 33%, this also results in the read loop not ending even after the rendering process is complete.
If you then try to close the app, the GUI also freezes…
The rest of the app—internally—has long been in an error-like state… or something like that… see screenshot; it keeps reading and reading, even 30 minutes after the job has long since finished…
@seifenchef I haven’t encountered any such HDD/SSD reading issues on my system (but I haven’t really paid attention to the SSD statistics so far); I suspect this has nothing to do with the problem where the app doesn’t close properly after rendering is complete.
@kyle.topazlabs I suspect that the problem with the frozen program window might be caused by the enabled Live Export feature or is related to it.
Steps to reproduce:
A) Launch the Topaz Video application (1.3.0 on Win11)
B) Open a video file (I used a MOV ProRes 422 HQ file) C) Change the setting: File > Preferences > Advanced > “Live Export” (*)
D) Select an upscaling model and click “Export”
E) Wait until rendering is complete
F) Close the application (either via the “X” in the upper-right corner or via the main menu “File > Exit”)
(*) If “Live Export” is enabled in step C, the application window will freeze when you try to close it at the end. This does not appear to happen when the “Live Export” feature is disabled. Don’t confuse the two: This refers to the “Live export” setting, not “Live render in preview”
However, I only ran a small test series consisting of 5–6 trials using a very short test video (4x upscaling with Gaia2). Therefore, it’s just a guess that this might be related.
We had this patched in 1.0.2 but some users have reported it came back in releases after that. We are still investigating, as there are a lot of different variables that seem to be at play when we have reviewed different users logs who are experiencing the issue.
In my personal tests I have not been able to reliably replicate the situation, even when closing the app while an export is actively running.
I will pass along those notes you ran and incorporate them into my own testing to see what happens.
It worked for me right away.
Ran several passes with ProRes.
No more ReadTerror, and the app closes “normally” now.
→ Absolutely constant speed from start to finish!
Okay, you don’t have the preview anymore where you could check—is the result okay, or should I quickly change something…
But at least this way I can do batch processing.
→ I disabled all features in the app…
The app now runs with virtually no load on the computer.
(Only FFMPEG.exe is using resources, of course…)
… the AI says: in hindsight, this makes sense…
… but we didn’t figure it out on our own…
