Recherche avancée

Sur d’autres sites (8341)

• StackOverflowException with Process in C#

  4 juin 2015, par user3633222

  I have a process, which runs in a console app. It runs forever.

  After a couple of days the app crashes with a StackOverflowException.

  The essence of the app is where I spin up a Process with FFMpeg.exe and creates a sceenshot of a video stream. It works very good but only for a few days at the time.

  I am pretty sure it has to do with the disposal of the FFMpeg or some internal Process stuff.

  Here is the code

  using ( Process ffmpegProcess = new Process() ) {
  
  
  
      //arguments for running ffmpeg
  
      ffmpegProcess.StartInfo.UseShellExecute = false;
  
      ffmpegProcess.StartInfo.CreateNoWindow = true;
  
      ffmpegProcess.StartInfo.RedirectStandardOutput = true;
  
  
  
      //specific for our screenshots
  
      ffmpegProcess.StartInfo.FileName = string.Concat( Environment.CurrentDirectory, Path.DirectorySeparatorChar, ffmpegProgramName );
  
  
  
      try {
  
          //todo: log this stopwatch somewhere perhaps
  
          processWatch.Start();
  
  
  
          //set arguments every time we want to create a new screen shot
  
          ffmpegProcess.StartInfo.Arguments = string.Format( @"-y -i {0}{1} -threads 0 -ss 00:00:01.000 -f image2 -s 620x349 -vframes 1 ../../web/{2}.jpg", server, streamPath, slug );
  
          ffmpegProcess.Start();
  
          ffmpegProcess.WaitForExit( 500 );
  
  
  
          Console.WriteLine( slug );
  
          Console.WriteLine( processWatch.Elapsed );
  
  
  
          processWatch.Reset();
  
          runCount++;
  
          cacheIndexer++;
  
  
  
          //lets see how many spins we've had!
  
          Console.WriteLine( string.Format( "SERVER CACHE INDEX : {0}", cacheIndexer ) );
  
          Console.WriteLine( string.Format( "RUN : {0}", runCount ) );
  
          Console.WriteLine( Environment.NewLine );
  
  
  
      } catch ( Exception ex ) {
  
          //Console.WriteLine( "Ex " + ex );
  
      }
  
  }

  The loop looks like this.

      public void RecurseTask() {
  
          /*
  
          You can try one of these, but you will se CPU usage go crazy and perhaps concurrency errors due IO blocking
  
  
  
          Parallel.ForEach( _videoStreamSlugs, ( e ) => _videoStreamScreenShots.GrabScreenShot( e ) );
  
  
  
          foreach ( var slug in _videoStreamSlugs ) {
  
              Task.Run( () => _videoStreamScreenShots.GrabScreenShot( slug ) );
  
          }
  
          */
  
  
  
          //we want to grab screen shots for every slug in out slug list!
  
          foreach ( var slug in _videoStreamSlugs ) {
  
              _videoStreamScreenShots.GrabScreenShot( slug );
  
          }
  
  
  
          //sleep for a little while
  
          Thread.Sleep( _recurseInterval );
  
  
  
          //A heavy clean up!
  
          //We do this, trying to avoid a stackoverflow excecption in the recursive method
  
          //Please inspect this if problems arise
  
          GC.Collect();
  
  
  
          //lets grab over again
  
          RecurseTask();
  
      }

  I added a GC.Collect out of curiosity to see if it made a difference.

  I am not doing a Windows Service.

• Call to Process works fine with Debug, but it doesn't work in the installed application

  6 février 2019, par Santi

  I am developing a Windows Form program that has callings to ffmpeg library through the class Process.

  It works fine when I run it with the Debug in Visual Studio 2013. But when I install the program and I invoke the operation that call to the ffmpeg Process, it doesn’t work. The cmd screen appears an disappears and nothing happens.

  I have tried to know what can be happening getting a log file with the output of ffmpeg, in case it was a problem in the ffmpeg libraries. However, after executing it the log is empty, what means that the ffmpeg command has not been executed.

  Can someone help me, please ?

  The code is this :

  ProcessStartInfo startInfo = new ProcessStartInfo();
  
  startInfo.FileName = "cmd.exe";
  
  startInfo.Arguments = "/c " + ffmpegPath + " " + commandArguments;
  
  using (Process processTemp = new Process())
  
  {
  
      processTemp.StartInfo = startInfo;
  
      processTemp.EnableRaisingEvents = true;
  
      processTemp.Start();
  
      processTemp.WaitForExit();
  
  }

  I am invoking to cmd.exe (not directly ffmpeg.exe) because in the arguments sometimes there can be a pipe (that is why the command starts with "/c").

• Java ffmpeg Process Broken Pipe on OSX

  30 juin 2015, par CrushedPixel

  We’re using ffmpeg to render a video from a Java Application.
  Therefore, a java.lang.Process is being used :

  Process process = new ProcessBuilder(command).directory(folder).start();
  
  OutputStream outputStream = process.getOutputStream();
  
  WritableByteChannel channel = Channels.newChannel(outputStream);

  In a new Thread, we’re writing the video to the WritableByteChannel :

  ByteBuffer byteBuffer = ByteBuffer.allocate(img.getWidth() * img.getHeight() * 4);
  
  byteBuffer.asIntBuffer().put(((DataBufferInt) imgBuffer).getData());
  
  channel.write(byteBuffer);

  On Windows and Linux machines, this code works very well. However, on my Mac OSX Yosemite Machine, the following error occurs :

  java.io.IOException: Broken pipe
  
      at java.io.FileOutputStream.writeBytes(Native Method)
  
      at java.io.FileOutputStream.write(FileOutputStream.java:326)
  
      at java.io.BufferedOutputStream.write(BufferedOutputStream.java:122)
  
      at java.nio.channels.Channels$WritableByteChannelImpl.write(Channels.java:458)
  
      at test.ffmpeg.VideoWriter$1.run(VideoWriter.java:109)
  
      at java.lang.Thread.run(Thread.java:745)

  I found an error report hinting to a similar malfunction in sbt here : https://github.com/sbt/sbt/issues/327

  Why does OSX close the Pipe and how can I prevent it ? ffmpeg is properly installed and can be used via command line.

  Thanks in advance for any suggestions !

  Greetings, CrushedPixel