File Locks not released correctly

Topaz Video AI Bugs and Issues
1

[If you are posting a new bug, please include the following]

  1. The bug / behavior you have encountered
    The file locks on output files are not released correctly after the file creation job completes. I can close the job, project and input file, but the output file locks are only released when Video AI application is closed. This problem has only started in version 7.0.0. I am unable to rename the output file until I close the entire application now.
  2. Your system profile
    Windows 11, Video AI 7.0.0. Files are being written to Samba Shared NAS.
  3. Your log files (Help > Logging > Get Logs for Support)
  4. Any screenshots as necessary

[Please be sure to have searched for your bug before posting. Duplicate posts will be removed.]

2

There‘s actually a way to confirm if thats the case or not without much trail and error:

Use MS Sysinternals “Handle” tool

Download Microsoft’s Handle utility: Handle - Sysinternals | Microsoft Learn

  • Open Command Prompt as admin
  • Run:
    handle output.mp4

You should see output like:
VideoAI.exe pid:1234 type: File C:\i\like\cats\yourfileoutput.mp4

If VideoAI.exe is listed, it confirms the app is still locking the file,

Cheers

3

Hi, Thanks for the quick response. I’ve confirmed it’s Topaz Video AI. It’s actually keeping both the original source file and the new output file handles open, even after the file is complete and I opt to close the input file.

Nthandle v5.0 - Handle viewer
Copyright (C) 1997-2022 Mark Russinovich
Sysinternals - www.sysinternals.com

Topaz Video AI.exe pid: 26332 type: File B90: \Device\Mup\nas.local\Videos\movie1.mkv

Nthandle v5.0 - Handle viewer
Copyright (C) 1997-2022 Mark Russinovich
Sysinternals - www.sysinternals.com

Topaz Video AI.exe pid: 26332 type: File 23B4: \Device\Mup\nas.local\Videos\movie1_prob4.mkv

This wasn’t an issue prior to v 7.0.0. I have my Windows 11 PC fully patched and up to date. My NAS is also fully up to date.

Kind Regards,

Philip

4

Hi, seems like the hunch was right!

Thanks for confirming that—and great job verifying it with nthandle.

I assume following:
If both the original input and the output file remain locked after the export completes and the input is manually closed, that strongly suggests a regression in file handle cleanup logic introduced in Video AI 7.0.0.

In versions prior to 7.x, the application likely released file handles either:

  • Immediately after export finished
  • Or upon closing the associated job/session

But in 7.0.0, it seems the process now retains an open handle to both source and output files until the entire app is exited, even if you explicitly close the input. This may point to:

  • A reference leak in the export thread or job management layer
  • A new file-watching or post-export validation mechanism (e.g. waveform caching or metadata scanning) that forgets to close its streams
  • Or a change in how the app handles NAS-based paths via SMB (MUP device layer), where flushing and handle release require explicit teardown

Given that it worked correctly in earlier versions, it’s definitely a behavior regression worth flagging for the dev team.

Cheers

1 Like
5

I have the same problem. Since I installed version 7, when a video finishes exporting, the copy that is made for Crash Recovery stays open, and copying data to the SSD. Even if I close Topaz Video AI is still running in the background copying data to the SSD, as I check in the Windows 11 Task Manager. Once I left it running for over half an hour, and it kept trying to copy data to the SSD.
I have to close Topaz manually from the Task Manager, so that everything stops.

6

I am still seeing this problem with files on my NAS, though primarily it’s now the output file that is consistently left with file handles open.