From: Wolfgang Haupt <haupt.wolfgang@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>, Srihari Sridhar <gshari9918@gmail.com> Subject: Re: [FFmpeg-devel] Issue - Error Due to higher number of threads Date: Thu, 19 May 2022 12:12:01 +0200 Message-ID: <f835c0e3-2d1a-6f63-ea1c-baa1254405e1@gmail.com> (raw) In-Reply-To: <CAL-t=HnmBtV3d-XNk5PWxDdgZ_0T7Kiuni3WPd0qk4ZiGEvCoQ@mail.gmail.com> > Hi, > > Thanks for the reply. I checked the memory usage while building ffmpeg with > 64 threads. The machine I tested has 128 GB ram. While I tested it I found > that maximum memory utilized by the build of ffmpeg was 17GB. Still the > build throws up error semaphore or child process wait (Error 87 : The > parameter is incorrect). Hence could you check on the same please. I have > attached screenshots of memory utilized from the task manager. What CPU are you on? There is some complexity regarding the amount of threads and process groups on windows, see: https://www.windowscentral.com/windows-10-pro-cant-handle-amd-threadripper-3990xs-128-threads Do you even have a processor that will utilize 64 cores? I recommend trying with smaller values and see where "windows make" starts to fail. > > Regards, > S Srihari > > On Thu, 12 May 2022 at 16:45, Timo Rothenpieler <timo@rothenpieler.org> > wrote: > >> On 12.05.2022 04:22, Srihari Sridhar wrote: >>> Hi, >>> >>> I was building ffmpeg through windows. While I was able to successfully >>> able to build for smaller number of threads, for larger number of >> threads I >>> faced an issue >>> >>> The commands I used were >>> bash ./configure --arch=x86 --target-os=mingw32 --disable-x86asm >>> make -j <no_of_Threads> >>> >>> While building with 4 Threads the build was successful >>> Screenshot: >>> [image: image.png] >>> >>> While building with 64 threads, I faced the following error, >>> Screenshot : >>> [image: image.png] >>> semaphore or child process wait (Error 87 : The parameter is incorrect) >> Please don't use images for plain text. It's hard to access and barely >> legible. >> >>> Please could you check this issue. Thanks >> You probably just ran out of RAM or something. Highly unlikely that this >> is an issue with ffmpeg. >> _______________________________________________ >> ffmpeg-devel mailing list >> ffmpeg-devel@ffmpeg.org >> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel >> >> To unsubscribe, visit link above, or email >> ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe". >> >> >> _______________________________________________ >> ffmpeg-devel mailing list >> ffmpeg-devel@ffmpeg.org >> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel >> >> To unsubscribe, visit link above, or email >> ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe". _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2022-05-19 10:12 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-12 2:22 Srihari Sridhar 2022-05-12 11:14 ` Timo Rothenpieler 2022-05-19 9:32 ` Srihari Sridhar 2022-05-19 10:12 ` Wolfgang Haupt [this message] 2022-05-23 12:30 ` Srihari Sridhar 2022-05-26 15:53 ` Srihari Sridhar
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=f835c0e3-2d1a-6f63-ea1c-baa1254405e1@gmail.com \ --to=haupt.wolfgang@gmail.com \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=gshari9918@gmail.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git