Recherche avancée

Sur d’autres sites (7522)

• javacv FFMPEG decode memory leak ?

  25 mars 2015, par Liquan Nie

  I’m new to JAVACV and I am using FFMPEG to play some video file as follows
  My enviroument is windows 8 with jdk7 and javacv0.10.

              String file_path ="D:\\1.mp4";
  
                  
  
                  // regist all format and codec
  
                  avformat.av_register_all();
  
                  avcodec.avcodec_register_all();
  
                  
  
                  // open file
  
                  avformat.AVFormatContext avFormatCtx = avformat.avformat_alloc_context();
  
                  if (avformat.avformat_open_input(avFormatCtx, file_path, null, null) != 0)
  
                  {
  
                          System.out.println("cann't open file\r\n");
  
                          return;
  
                  }
  
                  // find stream info
  
                  if (avformat.avformat_find_stream_info(avFormatCtx, (AVDictionary)null) < 0)
  
                  {
  
                          System.out.println("can't find stream info\r\n");
  
                          return;
  
                  }
  
  
  
                  int videoIndex = -1;
  
                  for(int i=0; i< avFormatCtx.nb_streams();i++)
  
                  {
  
                          if(avFormatCtx.streams(i).codec().codec_type() == avutil.AVMEDIA_TYPE_VIDEO)
  
                          {
  
                                  videoIndex = i;
  
                          }
  
                  }
  
                  // determ codec
  
                  avcodec.AVCodecContext avCodecCtx = avFormatCtx.streams(videoIndex).codec();
  
                  avcodec.AVCodec codec = avcodec.avcodec_find_decoder(avCodecCtx.codec_id());
  
                  if (codec == null)
  
                  {
  
                          System.out.println("codec not found");
  
                          return;
  
                  }
  
                  if(avcodec.avcodec_open2(avCodecCtx, codec, (AVDictionary)null) < 0)
  
                  {
  
                          System.out.println("cann't open avcodec\r\n");
  
                  }
  
                  avutil.AVFrame frame    = avcodec.avcodec_alloc_frame();
  
                  avutil.AVFrame frameRGB = avcodec.avcodec_alloc_frame();
  
                  int numByte = avcodec.avpicture_get_size(avutil.AV_PIX_FMT_RGB24, avCodecCtx.width(), avCodecCtx.height());
  
                  Pointer outBuffer = avutil.av_malloc(numByte);
  
                  
  
                  avcodec.avpicture_fill(new AVPicture(frameRGB), outBuffer.asByteBuffer(), avutil.AV_PIX_FMT_RGB24, avCodecCtx.width(), avCodecCtx.height());
  
                  avformat.av_dump_format(avFormatCtx, 0, file_path, 0);
  
                  System.out.println(avFormatCtx.duration());
  
                  SwsContext img_convert_ctx = swscale.sws_getContext(avCodecCtx.width(), avCodecCtx.height(), avCodecCtx.pix_fmt(), avCodecCtx.width(), avCodecCtx.height(), avutil.AV_PIX_FMT_RGB24, swscale.SWS_BICUBIC, null, null, (double[])null);
  
  
  
                  AVPacket pkt = new AVPacket();
  
                  int y_size = avCodecCtx.width()*avCodecCtx.height();
  
                  avcodec.av_new_packet(pkt, y_size);
  
                  opencv_highgui.cvNamedWindow(WINDOW_NAME);
  
                  
  
                  IplImage showImage = opencv_core.cvCreateImage(opencv_core.cvSize(avCodecCtx.width(), avCodecCtx.height()), opencv_core.IPL_DEPTH_8U, 3);
  
                  // read frames loop
  
                  int frameNumbers = avformat.av_read_frame(avFormatCtx, pkt);
  
              System.out.println("frame number is "+frameNumbers);
  
              
  
              while (avformat.av_read_frame(avFormatCtx, pkt) >= 0)
  
                  {
  
                      //System.out.println(pkt.asByteBuffer());
  
                          if (pkt.stream_index() == videoIndex)
  
                          {
  
                                  IntPointer ip = new IntPointer();
  
                                  int ret = avcodec.avcodec_decode_video2(avCodecCtx, frame, ip, pkt);
  
                                  if (ret < 0)
  
                                  {
  
                                          System.out.println("codec error\r\n");
  
                                          return;
  
                                  }
  
                                  
  
                                  if (ip.get()!= 0)
  
                                  {
  
                                          swscale.sws_scale(img_convert_ctx, frame.data(), frame.linesize(), 0, avCodecCtx.height(), frameRGB.data(), frameRGB.linesize());
  
                                          showImage.imageData(frameRGB.data(0));
  
                                          
  
                                          showImage.widthStep(frameRGB.linesize().get(0));
  
                                          opencv_highgui.cvShowImage(WINDOW_NAME, showImage);
  
                                          opencv_highgui.cvWaitKey(25);
  
                                  }
  
                          }
  
                  }
  
                  
  
                  showImage.release();
  
                  opencv_highgui.cvDestroyWindow(WINDOW_NAME);
  
                  avutil.av_free(frameRGB);
  
                  avcodec.avcodec_close(avCodecCtx);
  
                  avformat.avformat_close_input(avFormatCtx);

  but i run into get this error

  # A fatal error has been detected by the Java Runtime Environment:
  
  #
  
  #  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00000000767c35ed, pid=11884, tid=3960
  
  #
  
  # JRE version: 7.0_13-b20
  
  # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.7-b01 mixed mode windows-amd64 compressed oops)
  
  # Problematic frame:
  
  # C  [avcodec-56.dll+0x4835ed]  avcodec_decode_video2+0xbd
  
  #
  
  # Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
  
  #
  
  # An error report file with more information is saved as:
  
  # E:\code\android\TestJAVACV\hs_err_pid11884.log
  
  #
  
  # If you would like to submit a bug report, please visit:
  
  #   http://bugreport.sun.com/bugreport/crash.jsp
  
  # The crash happened outside the Java Virtual Machine in native code.
  
  # See problematic frame for where to report the bug.
  
  #
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'D:\1.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      creation_time   : 1970-01-01 00:00:00
  
      encoder         : Lavf53.29.100
  
    Duration: 00:08:30.27, start: 0.000000, bitrate: 160 kb/s
  
      Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 960x540 [SAR 1:1 DAR 16:9], 28 kb/s, 15 fps, 15 tbr, 15 tbn, 30 tbc (default)
  
      Metadata:
  
        creation_time   : 1970-01-01 00:00:00
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 127 kb/s (default)
  
      Metadata:
  
        creation_time   : 1970-01-01 00:00:00
  
        handler_name    : SoundHandler

  and in the log file i found that the enden space heap in jvm has been used 98%. but I don’t know where is the issue, since the document of ffmpeg is not that enough, I feel difficult to know more about how to use it well ,any suggestions ??

  Heap
  
   PSYoungGen      total 23872K, used 20250K [0x00000000e5600000, 0x00000000e70a0000, 0x0000000100000000)
  
    eden space 20480K, 98% used [0x00000000e5600000,0x00000000e69c69f8,0x00000000e6a00000)

• Generating test data – Introducing the Piwik Platform

  9 octobre 2014, par Thomas Steur — Development

  This is the next post of our blog series where we introduce the capabilities of the Piwik platform (our previous post was How to create a command). This time you’ll learn how to generate test data.

  Developers are developing on their local Piwik instance which usually does not contain useful data compared to a real Piwik installation in production (only a few test visits and a few tests users and websites). The ‘VisitorGenerator’ plugin lets you generate any number of visits, websites, users, goals and more. The generator makes sure there will be data for each report so you can easily test anything.

  Getting started

  In this series of posts, we assume that you have already installed Piwik. If not, visit the Piwik Developer Zone where you’ll find the Installation guide for developers.

  Installing the VisitorGenerator plugin

  The easiest way to install the plugin is by using the Marketplace in Piwik itself. It is accessible via Settings => Marketplace => Get new functionality. There you’ll find the plugin “VisitorGenerator” which you can install and activate in one click.

  If your Piwik instance is not connected to the internet you can download the plugin from the VisitorGenerator page on the Marketplace. Afterwards you can install the plugin by going to Settings => Marketplace => Uploading a plugin and uploading the previously downloaded ZIP file.

  If you have already installed the plugin make sure it is activated by going to Settings => Plugins.

  Generating websites

  After you have installed the plugin you can add as many websites as you need. This is useful for instance when you want to test something that affects many websites such as the ‘All Websites’ dashboard or the Websites manager. To generate any number of websites use the following command :

  ./console visitorgenerator:generate-website --limit=10

  This will generate 10 websites. If you need more websites simply specify a higher limit. In case you are wondering the names and URLs of the websites are randomly generated by the Faker PHP library.

  Generating goals

  In case you want to test anything related to Goals you should execute the following command :

  ./console visitorgenerator:generate-goals --idsite=1

  This will generate a few goals for the specified site. The generated goals are defined in a way to make sure there will be conversions when generating the visits in the next step.

  Generating visits

  To generate visits there are two possibilities. Either via the Piwik UI by going to Settings => Visitor Generator or by using the command line. The UI is a bit limited in generating visits so we recommend to use the command line. There you can generate visits as follows :

  ./console visitorgenerator:generate-visits --idsite=1

  This will generate many different visits for the current day. Don’t worry if it takes a while, it will insert quite a few visits by default.

  In case you want to generate visits for multiple days in the past as well you can specify the --days option.

  ./console visitorgenerator:generate-visits --idsite=1 --days=5

  Providing your own logs

  Half of the generated visits are randomly generated and half of the visits are based on real logs to make sure there is data for each report. If you want to generate visits based on your own logs for a more realistic testing just place your log files in the plugins/VisitorGenerator/data folder and make sure the file name ends with .log. You can find a few examples in the VisitorGenerator data folder.

  To generate visits based only on real log files then use the --no-fake option.

  ./console visitorgenerator:generate-visits --idsite=1 --no-fake

  All generated visits will come from the logs and no random visits nor random fake data will be used.

  Advanced features

  We are regularly adding new commands, tools and runtime checks to make your life as a developer easier. For instance you can also generate users and annotations. In the future we want to extend the plugin to create visits in the background to make sure there will be constantly new actions in the real time report.

  Are you missing any kind of generator or any other feature to make your life as a developer easier ? Let us know by email, we are listening !

  Would you like to know more about the Piwik platform ? Go to our Piwik Developer Zone where you’ll find guides and references on how to develop plugin and themes.

• Generating test data – Introducing the Piwik Platform

  9 octobre 2014, par Thomas Steur — Development

  This is the next post of our blog series where we introduce the capabilities of the Piwik platform (our previous post was How to create a command). This time you’ll learn how to generate test data.

  Developers are developing on their local Piwik instance which usually does not contain useful data compared to a real Piwik installation in production (only a few test visits and a few tests users and websites). The ‘VisitorGenerator’ plugin lets you generate any number of visits, websites, users, goals and more. The generator makes sure there will be data for each report so you can easily test anything.

  Getting started

  In this series of posts, we assume that you have already installed Piwik. If not, visit the Piwik Developer Zone where you’ll find the Installation guide for developers.

  Installing the VisitorGenerator plugin

  The easiest way to install the plugin is by using the Marketplace in Piwik itself. It is accessible via Settings => Marketplace => Get new functionality. There you’ll find the plugin “VisitorGenerator” which you can install and activate in one click.

  If your Piwik instance is not connected to the internet you can download the plugin from the VisitorGenerator page on the Marketplace. Afterwards you can install the plugin by going to Settings => Marketplace => Uploading a plugin and uploading the previously downloaded ZIP file.

  If you have already installed the plugin make sure it is activated by going to Settings => Plugins.

  Generating websites

  After you have installed the plugin you can add as many websites as you need. This is useful for instance when you want to test something that affects many websites such as the ‘All Websites’ dashboard or the Websites manager. To generate any number of websites use the following command :

  ./console visitorgenerator:generate-website --limit=10

  This will generate 10 websites. If you need more websites simply specify a higher limit. In case you are wondering the names and URLs of the websites are randomly generated by the Faker PHP library.

  Generating goals

  In case you want to test anything related to Goals you should execute the following command :

  ./console visitorgenerator:generate-goals --idsite=1

  This will generate a few goals for the specified site. The generated goals are defined in a way to make sure there will be conversions when generating the visits in the next step.

  Generating visits

  To generate visits there are two possibilities. Either via the Piwik UI by going to Settings => Visitor Generator or by using the command line. The UI is a bit limited in generating visits so we recommend to use the command line. There you can generate visits as follows :

  ./console visitorgenerator:generate-visits --idsite=1

  This will generate many different visits for the current day. Don’t worry if it takes a while, it will insert quite a few visits by default.

  In case you want to generate visits for multiple days in the past as well you can specify the --days option.

  ./console visitorgenerator:generate-visits --idsite=1 --days=5

  Providing your own logs

  Half of the generated visits are randomly generated and half of the visits are based on real logs to make sure there is data for each report. If you want to generate visits based on your own logs for a more realistic testing just place your log files in the plugins/VisitorGenerator/data folder and make sure the file name ends with .log. You can find a few examples in the VisitorGenerator data folder.

  To generate visits based only on real log files then use the --no-fake option.

  ./console visitorgenerator:generate-visits --idsite=1 --no-fake

  All generated visits will come from the logs and no random visits nor random fake data will be used.

  Advanced features

  We are regularly adding new commands, tools and runtime checks to make your life as a developer easier. For instance you can also generate users and annotations. In the future we want to extend the plugin to create visits in the background to make sure there will be constantly new actions in the real time report.

  Are you missing any kind of generator or any other feature to make your life as a developer easier ? Let us know by email, we are listening !

  Would you like to know more about the Piwik platform ? Go to our Piwik Developer Zone where you’ll find guides and references on how to develop plugin and themes.