As noted in my original post, my CreateProcess() function works just fine as
it is configured.
It's been running in a production environment for over 10 years.
Yes, I used the MS Win32 structure, and properly clear the fields before
initialization.
As noted above, the fix was changing from "Full" to "Essential" ffmpeg.
Using Essentials, it runs perfectly.
On Monday, October 13, 2025 at 01:18:54 AM PDT, Tobias Rapp via ffmpeg-user
<[email protected]> wrote:
On 13/10/2025 06:53, Bruce Gavin via ffmpeg-user wrote:
> Win10 latest version and updates.
> Running on ESXi 6.7 VMFull Version 8.0 from your download page.Spawning
> platform is Delphi 7 Enterprise.
> I am willing to do any debug steps you require.
>
> On Sunday, October 12, 2025 at 09:21:07 PM PDT, Gyan Doshi via
>ffmpeg-user<[email protected]> wrote:
>
>
>
> On 2025-10-13 05:09 am, Bruce Gavin via ffmpeg-user wrote:
>> I am attempting to spawn ffmpeg to do a simple integrity check on MP3 files.
>> I have a working process that spawns other EXE without problems.
>> I moved ffmpeg.exe from C:\Windows to C:\ and the error is the same.
>> I attempt to spawn ffmpeg.exe without any command parameters to get a help
>> screen.
>> With or without parameters the access exception is the same.
>> Q: What am I missing?
I guess the most relevant part when calling CreateProcess() is the
STARTUPINFO structure. Do you clear the structure properly before
setting its fields? How do you initialize the handles for standard
output/error? See the official Win32 API documentation
<https://learn.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-createprocessw>
for reference.
Regards, Tobias
_______________________________________________
ffmpeg-user mailing list -- [email protected]
To unsubscribe send an email to [email protected]
_______________________________________________
ffmpeg-user mailing list -- [email protected]
To unsubscribe send an email to [email protected]
