Recherche avancée

Sur d’autres sites (7111)

• avcodec/vp3 : Check eob_run

  9 février 2018, par Michael Niedermayer

  avcodec/vp3 : Check eob_run
  Fixes : out of array access
  
  Fixes : 5919/clusterfuzz-testcase-minimized-5859311382167552
  
  Fixes : special case for theora (untested due to lack of sample)
  Found-by : continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
  
  Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
  

  • [DH] libavcodec/vp3.c

• ffmpeg azure function consumption plan low CPU availability for high volume requests

  27 novembre 2017, par The Lemon

  I am running an azure queue function on a consumption plan ; my function starts an FFMpeg process and accordingly is very CPU intensive. When I run the function with less than 100 items in the queue at once it works perfectly, azure scales up and gives me plenty of servers and all of the tasks complete very quickly. My problem is once I start doing more than 300 or 400 items at once, it starts fine but after a while the CPU slowly goes from 80% utilisation to only around 10% utilisation - my functions cant finish in time with only 10% CPU. This can be seen in the image shown below.
  Does anyone know why the CPU useage is going lower the more instances my function creates ? Thanks in advance Cuan

  edit : the function is set to only run one at a time per instance, but the problem exists when set to 2 or 3 concurrent processes per instance in the host.json

  edit : the CPU drops get noticeable at 15-20 servers, and start causing failures at around 60. After that the CPU bottoms out at an average of 8-10% with individuals reaching 0-3%, and the server count seems to increase without limit (which would be more helpful if I got some CPU with the servers)

  Thanks again, Cuan.

  I’ve also added the function code to the bottom of this post in case it helps.

  

  

  using System.Net;
  
  using System;
  
  using System.Diagnostics;
  
  using System.ComponentModel;
  
  
  
  public static void Run(string myQueueItem, TraceWriter log)
  
  {
  
      log.Info($"C# Queue trigger function processed a request: {myQueueItem}");
  
      //Basic Parameters
  
          string ffmpegFile = @"D:\home\site\wwwroot\CommonResources\ffmpeg.exe";
  
          string outputpath = @"D:\home\site\wwwroot\queue-ffmpeg-test\output\";
  
          string reloutputpath = "output/";
  
          string relinputpath = "input/";
  
          string outputfile = "video2.mp4";
  
          string dir =  @"D:\home\site\wwwroot\queue-ffmpeg-test\";
  
  
  
      //Special Parameters
  
  
  
          string videoFile = "1 minute basic.mp4";
  
          string sub = "1 minute sub.ass";
  
      //guid tmp files
  
  
  
          // Guid g1=Guid.NewGuid();
  
          // Guid g2=Guid.NewGuid();
  
          // string f1 = g1 + ".mp4";
  
          // string f2 = g2 + ".ass";
  
          string f1 = videoFile;
  
          string f2 = sub;
  
      //guid output - we will now do this at the caller level
  
          string g3 = myQueueItem;
  
          string outputGuid = g3+".mp4";
  
      //get input files
  
      //argument
  
          string tmp = subArg(f1, f2, outputGuid );
  
      //String.Format("-i \"" + @"input/tmp.mp4" + "\" -vf \"ass = '" + sub + "'\" \"" + reloutputpath +outputfile + "\" -y");
  
      log.Info("ffmpeg argument is: "+tmp);
  
  
  
  
  
      //startprocess parameters
  
      Process process = new Process();
  
      process.StartInfo.FileName = ffmpegFile;
  
      process.StartInfo.Arguments =  tmp;
  
      process.StartInfo.UseShellExecute = false;
  
      process.StartInfo.RedirectStandardOutput = true;
  
      process.StartInfo.RedirectStandardError = true;
  
      process.StartInfo.WorkingDirectory = dir;
  
      //output handler
  
  
  
      process.OutputDataReceived += new DataReceivedEventHandler(
  
          (s, e) => 
  
          { 
  
              log.Info("O: "+e.Data);
  
          }
  
      );
  
      process.ErrorDataReceived += new DataReceivedEventHandler(
  
          (s, e) => 
  
          { 
  
              log.Info("E: "+e.Data);
  
          }
  
      );
  
      //start process
  
      process.Start();
  
      log.Info("process started");
  
      process.BeginOutputReadLine();
  
      process.BeginErrorReadLine();
  
      process.WaitForExit();
  
  }
  
  public static void getFile(string link, string fileName, string dir, string relInputPath){
  
      using (var client = new WebClient()){
  
          client.DownloadFile(link, dir + relInputPath+ fileName);
  
          }
  
  
  
  }
  
  public static string subArg(string input1, string input2, string output1){
  
      return String.Format("-i \"" + @"input/" +input1+ "\" -vf \"ass = '" + @"input/"+input2 + "'\" \"" + @"output/" +output1 + "\" -y");
  
  
  
  }

• Secure and track every change to your Piwik installation with the Activity Log plugin

  14 novembre 2017, par InnoCraft — Plugins

  Are you wondering how your colleagues are using Piwik ? Would you like to know if an unauthorized user got an access to your installation ? Would you like to remember the last actions you performed in Piwik some weeks ago ? At InnoCraft, we developed a plugin called “Activity Log”. With this feature you can easily track and check all major changes to your Piwik websites, for example : user permissions, goals, and funnels. In this article we will show you the different ways you can use it and explain why it is an invaluable plugin.

  Activity log for better security

  The activity log feature has been designed for security. Also referred to as “audit logging” or “audit trail”, with this plugin you will be able to :

  1. detect any suspicious actions
  2. detect hacker attacks
  3. help identify performance problems
  4. see clearly who did what, and when
  5. find out how people are using Piwik within your company

  1 – detect any suspicious actions

  With audit trail you can easily identify if a former employee still has access to your Piwik installation. You will then be able to know when he accessed it for the last time, and what changes she or he performed. If you got hacked, you will be able to find out if the user created, changed, or deleted any website, goals, or did anything else suspicious.

  2 – detect hacker attacks

  When an unregistered user is trying to access your Piwik, each failed login attempt is registered within the Activity Log report.

  3 – help identify performance problems

  Activity Log can help you identify performance problems by registering the sequence of each major action a user performed. For example, if a user updated or installed a third party plugin, and suddenly Piwik is getting performance problems, then it is likely that the plugin update caused it.

  4 – see clearly who did what, and when

  It is always challenging in an organization to know who did what and when. With Activity Log, you will know who were the employee(s) that accessed Piwik, created, updated, or deleted a goal, a funnel, a scheduled report, and much more.

  5- find out how people are using Piwik within your company

  By having a look at how people are using Piwik you will have an overview of how your colleagues use Piwik. For example, you can see who is creating Custom segments to analyse the audience in more details, who is creating funnels to learn where your users drop off. You will then be able to identify who has the knowledge and who needs training.

  Did you know ?

  You can help the Piwik core team make Piwik even better by sharing anonymously how you use Piwik on a day to day basis. You just need to install the following plugin : http://plugins.piwik.org/AnonymousPiwikUsageMeasurement

  What’s in it ?

  Once downloaded and installed from the marketplace, you will be able to access the activity log from the admin panel within the diagnostic section :

  

  If you are logged as a super user administrator, you will get an overview and a detailed report about who accessed Piwik and which actions they performed.

  Those reports are critical as they allow the super user to :

  • ensure users are following all documented procedures within your organization such as naming conventions for reports, using the right settings when adding measurables…
  • identify suspicious behavior. As those reports are gathering all major Piwik users activities it is easy to identify non conventional behavior.
  • replay the sequence some users went through in order to fix any potential issues.

  Activity log view report you can access through the admin panel

  So you will see in a second if an unusual user got access to Piwik and the different actions the user performed.
  It is also a good way to see the features that your users are using and identify potential misuse.

  As a regular user or admin, activity log is providing only the historical actions that this user performed :

  

  Actions listed in the log include any changes (add, edit, delete) to the following features (this is a non exhaustive list) :

  • Annotation
  • Custom Alert
  • Custom Dimension
  • Goal
  • Privacy settings
  • Scheduled report
  • Segment
  • User
  • Website
  • …

  This is a ideal to remember the actions they previously performed some weeks/months ago.

  Where can I start from here ?

  Activity log is a premium feature you can acquire through the Piwik marketplace. If you want to experience it before purchasing it, you can try it for free on our cloud infrastructure.

  I want to try the Activity Log plugin

  Activity log is just one out of the many great premium features developed by InnoCraft, the company founded by the creators of Piwik. Discover all their special plugins through the premium marketplace.