Recherche avancée

Sur d’autres sites (12190)

• http: fix potentially dangerous whitespace skipping code

  8 mars 2018, par wm4

  http: fix potentially dangerous whitespace skipping code
  If the string consists entirely of whitespace, this could in theory
  
  continue to write '\0' before the start of the memory allocation. In
  
  practice, it didn't really happen : the generic HTTP header parsing code
  
  already skips leading whitespaces, so the string is either empty, or
  
  consists a non-whitespace. (The generic code and the cookie code
  
  actually have different ideas about what bytes are whitespace : the
  
  former uses av_isspace(), the latter uses WHITESPACES. Fortunately,
  
  av_isspace() is a super set of the http.c specific WHITESPACES, so
  
  there's probably no case where the above assumption could have been
  
  broken.)
  

  • [DH] libavformat/http.c

• IIS Worker Process memory keeps increasing while asp.net run ffmpag process

  27 mars 2016, par cheinan

  I am running this code every 4 second

  protected string output = string.Empty;
  
  protected Process process;
  
  protected StreamReader sr;
  
  
  
  protected void Page_Load(object sender, EventArgs e)
  
  {
  
      process = new Process();
  
      process.StartInfo.Arguments = "-an -flv_metadata 1 -analyzeduration 1 -i \"rtmp://localhost/test/testStream live=1\" -s 700*394 -r 5 -vframes 10 -f image2pipe -";
  
      process.StartInfo.FileName = Page.MapPath("ffmpeg.exe");
  
      process.StartInfo.UseShellExecute = false;
  
      process.StartInfo.RedirectStandardOutput = true;
  
      process.StartInfo.CreateNoWindow = true;
  
      process.EnableRaisingEvents = true;
  
      process.Start();
  
  
  
      sr = process.StandardOutput;
  
      output = sr.ReadToEnd();
  
      process.WaitForExit();
  
  
  
      if (output.Length > 200)
  
      {
  
          process.Close();
  
          if (process != null)
  
          {
  
              process.Dispose();
  
              if (process != null)
  
              {
  
                  try { process.Kill(); }
  
                  catch { }
  
                  process = null;
  
              }
  
          }
  
      }
  
  }

  I using asp.net c# to run a FFmpeg process in order to get image data
  from rtmp stream
  the code is working fine but the problem is
  IIS Worker Process memory keeps increasing.

  I tried to use the using statement
  and :
  Close,
  Dispose,
  Kill,
  process = null
  but nothing help

  How I can stop this memory from increasing ?
  Is there a better way to control IIS Worker Process memory
  from asp.net c# code ?

• how to get the output of a child process in a variable c#

  4 août 2022, par Dokoa

  I want to get width, height information into a variable after ffprobe is finished.

  


  int width, height;   
Process pr = new Process();
                pr.StartInfo.FileName = "ffprobe";
                pr.StartInfo.Arguments = $"- v error - select_streams v: 0 - show_entries stream = width,height - of default = nw = 1 input.mp4";
                pr.StartInfo.UseShellExecute = false;
                pr.StartInfo.CreateNoWindow = true;
                pr.EnableRaisingEvents = true;
                pr.Start();


  


  example of ffprobe console output

  


  width=320
height=180