[Bug] CCExtractor 0.96 x64 Debug build displays error message at end of runs on Windows 11 PC

[TPeterson94070]

To reproduce this bug,

1. Unzip CCExtractor Windows x64 Debug build into a new folder
2. Copy a video file containing cc into that folder also
3. Open a Terminal window in the new folder and execute:
   .\ccextractorwinfull.exe .\<name of video file>
4. Note that the expected .srt files are created, but the below error message is displayed also.

The same bug occurs also in the x86 Debug package and may be demonstrated in the same way as above.

[cfsmp3]

@TPeterson94070 Can you try 0.96.6? Long shot, but I found something that could be related.

[rhythmcache]

#2129

[TPeterson94070]

@cfsmp3, sorry, got the same error with 0.96.6 Debug build.

[ansh27singh]

@TPeterson94070
I got the error causing line of code
Just simply remove the freep()

freep(&ccx_options.enc_cfg.output_filename);
Or either make it a comment.

I had modified the code and it's running perfectly, i will upload it on GitHub just asking for your approval

[TPeterson94070]

@ansh27singh, thanks for your interest and work. I see that @cfsmp3 has already merged #2129 from @rhythmcache today. I think that is the same fix as you're proposing.

[ansh27singh]

@ansh27singh, thanks for your interest and work. I see that @cfsmp3 has already merged #2129 from @rhythmcache today. I think that is the same fix as you're proposing.

I am happy to work with CCExtractor, If the issue is resolved so now I can focus on another issue of CCExtractor.

[Atul-Chahar]

I've submitted a fix for this issue: #2147

Root Cause: Double-free in multiprogram encoder initialization. The output_filename was being freed immediately after passing to init_encoder(), but the encoder also frees it during cleanup - causing a double-free that only Debug builds detect.

Fix: Removed the premature free (1 line deletion in lib_ccx.c).

The fix is ready for review.

[TPeterson94070]

@Atul-Chahar , I tested the x64 release build from yesterday's artifact here: https://github.com/CCExtractor/ccextractor/actions/runs/22418452471 and it already did not crash the way that the above-referenced builds did. So I cannot tell if PR #2147 is needed.